I have the solution installed, but stakeholders asked that when users click the cancel button before changing their password, or the continue button after successfully changing their password on /_Layouts/15/FBA/ChangePassword.aspx that the user be logged out so they have to re-login to the site with their newly changed password.
So i went to the FBAPackChangePasswordWebPart.resx located here: C:\Program Files\Common Files\microsoft shared\Web Server Extensions\15\Resources and added the url suffix: /_layouts/closeConnection.aspx?loginasanotheruser=true into the CancelDestinationPageUrl_DefaultValue entry and the ContinueDestinationPageUrl_DefaultValue entry.
I then pulled up the site in an incognito window from Chrome, signed in, navigated to the change password page, clicked the Cancel button, but was not logged out. Now if I manually add this url suffix to the url in the open incognito window, I am logged out, so I know the url is correct.
I thought the point of the resx file was that I could make changes to the entries on the fly without having to rebuild the solution, and I guess I could be wrong about this assumption.
So do these entries have to be made in development and built and deployed, or am I making this change in the wrong place?