Trying to reach the password/complete page, getting redirected.
-
Re: Redirect the user to a different URI for the forgot password flow
Hello, I was curious to ask if not including the client_id is the only way one can have users reach the password/complete page from password/change? My issue here is that password resets triggered from the oauth page will always contain a client_id and redirect_uri pointing at our client's oauth-redirect page. When I attempt to edit the information contained in our "reset password" link, not including a redirect_uri or directing it to my http://localhost:9011/password/complete creates errors, and I'd rather not not include the client_id since we need it for styling purposes. Is there any other way to achieve this?
-
@agalemmo I'm not sure I'm following. It sounds like you are saying:
- I want folks to reach the password complete page
- I want the client_id to be present (for styling)
- But I don't want the redirect_uri, because that sends the user elsewhere
Is that correct?
Would it be helpful to you to add another redirect_uri (you can have multiple configured for an application) that took someone to a 'password change complete' page that you (not FusionAuth) hosted?
