Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stage to redirect to another flow #2438

Closed
sevmonster opened this issue Mar 6, 2022 · 1 comment
Closed

Stage to redirect to another flow #2438

sevmonster opened this issue Mar 6, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@sevmonster
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Now that I will be able to handle password resets, user info updates, etc. in a more sane way with authentik thanks to #2397, I am implementing flows for them. While testing, I noticed that a user can still get to a recovery flow even if they are already signed in. Since recovery flows are designed for unauthenticated/unidentified users to recover their account as far as I know, it would be good UX to redirect the user to the appropriate flow for authenticated users that matches the same functionality as the recovery flow. I do not believe there is currently a way to do this.

Describe the solution you'd like
Add a stage to redirect the user to another flow. For my use case, policies could be used to check if the user is authenticated to activate the redirect.
This proposed stage could have configuration to pass the current context, or the ability to return to the calling flow after the called flow completes. Aside from my use case, this would also allow nested, reusable flows for complicated deployments to help cut down on redundancy, though this is just a hypothetical and not related to my use case.

Describe alternatives you've considered
Use deny stage if the user is authenticated, or implement the simple and complex recovery flows in one flow and use policies to only show specific stages depending on authentication state. The former is not user friendly and the latter is unnecessarily complex in my opinion.

@BeryJu
Copy link
Member

BeryJu commented Jul 2, 2022

should be closed by #3192

@BeryJu BeryJu closed this as completed Jul 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants