I am using ACUL screens for forgot password and reset password. The user will get an email OTP, enter it on email-identifier-challenge screen and then change their password on the reset-password screen. Afterward, they are sent back to our home URL: …/sign-in. When the user is redirected to our sign in page, we want a banner to display showing whether or not the reset password was successful. I was hoping to implement this banner using a redirect with URL parameters. In the auth0 action post-change-password, it says redirects are not allowed. How would I go about this?
Hi @kaeb.sidney,
Welcome back to the Auth0 Community!
I understand that you are asking for some information on how to redirect users using URL parameters within Auth0 Actions.
To implement a redirect with custom URL parameters after a password reset, you cannot use a post-change-password Action. In Auth0, the post-change-password flow is an asynchronous, non-blocking trigger designed primarily for background operations (such as notifying internal systems or clearing downstream sessions) and does not support browser redirections.
The correct way to redirect users with custom URL parameters after a password reset is by using the synchronous Password Reset Post Challenge Action trigger. Auth0 provides this dedicated, blocking Action trigger which runs after the user successfully completes the first challenge (the email OTP in your ACUL flow) but before the transaction completes.
You can use this trigger to dynamically override and configure the final redirect URL (the result_url) using the api.transaction.setResultUrl() method. You can check out more under this KBA, which provides a sample action as well - Redirect Users After Password Reset with Actions, as well as the solutions provides in this article - Conditionally Redirect Users After a Password Reset in New Universal Login.
As this article also points, since you are using the Advanced Customization for Universal Login (ACUL) screens, please ensure you remove the Default Login Route configurations at both the application and tenant levels. If these default routes are left populated, Auth0’s default routing behavior will take precedence, overriding your custom Action.
I hope this helps and if you have further questions please let me know!
Kind regards,
Remus