Confirm registration with authorizedCallback
See original GitHub issueWhat is the right way to confirm email and redirect to client application already authorized?
Since we come from outside our application we have no local_state and state verification doesn’t pass with
ValidateStateFromHashCallback failed, state: undefined local_state:
authorizedCallback incorrect state
All attempts to pass an empty state have failed (and I guess if it was success it would cause security issue). Now I have an auto-login component to catch failed authorization result and redirect to. But I think it’s not right way.
Any suggestions?
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
authorizedCallback incorrect nonce after token refresh #592
i have set up an angular app according to the manual for an code based standard flow. login works but after token refresh...
Read more >API Applications - HELP CENTER - NICE
Instructions include registering an internal app and monitoring the performance ... In the Authorized Callback URLs field, enter a location where you want ......
Read more >Validate state and nonce in oidc-client - Stack Overflow
So I have debugged the code and found the questions for your answers,. The nonce value is per session or per user request?...
Read more >ASP.NET Core Identity Series – External provider ...
When registering a new account through the normal process, a confirmation email is sent to the email address used. The email contains a...
Read more >eBay Services: Registration: Confirm
Step 3 - Confirm Your Registration Part 1 of 2 · Click "I Accept" at the bottom of this page to accept the...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@john-hi could you try this with 6.0.12?
Make sure you have silent renew configured correctly and you should no longer have to redirect from your angular app after step 6 (above).
@damienbod I believe this can be closed…
Also… awesome how many issues were able to be closed by 6.0.12!
@damienbod this is one of those situstions where that refreshsession() call in the getisauthorized would prevent all the redirecting.