Identify hydra email verfication problem #3703
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note: This is not a fix, this is a POC to identify the problem
Related issue(s)
#3358
#3320
Problem: When completing a sign up coming from hydra (registration flow with login_challenge), even with show_verification_ui configured in post registrition hook, it doesn't jump to verfication page, but logined to hydra direct, and succesfully grant an oauth2 token.
This breaks our security model which relies our private email account.
This patch helps to identify the problem, it work as expected, when completing a sign up, it redirects to verfication page.
Checklist
introduces a new feature.
contributing code guidelines.
vulnerability. If this pull request addresses a security vulnerability, I
confirm that I got the approval (please contact
[email protected]) from the maintainers to push
the changes.
works.