- Issue created by @lfersoy
- Merge request !27Issue #3542974: Destination parameter not respected on login → (Open) created by lfersoy
I've opened a PR with the proposed changes. Please take a look when you have a chance.
When TFA features are enabled and the “Users optionally can enable” pathway is selected, users without TFA enabled are not redirected to the specified destination after login when a destination parameter is present in the path.
1. Set TFA features as Active and select “Users optionally can enable” as the default pathway.
2. Log in with a user who does not have Email TFA enabled on their account.
Example: Log in with /user/login?destination=/admin/config/people/email-tfa
3. The user is not redirected to the destination path after login.
Ensure the destination parameter from the request query is reapplied when falling back to the default login process.
Active
2.0
Code
I've opened a PR with the proposed changes. Please take a look when you have a chance.