-
Notifications
You must be signed in to change notification settings - Fork 54
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
Intermittent 500 /authorization-code/callback Blazor #273
Comments
@cagnew-lear Thanks for bringing this to our attention, and I apologize for the delayed response. I've opened an internal issue for tracking and prioritization. OKTA-852185 |
Hi Bryan - While trying to get it replicated, we did catch something which may be part of this. I'm not sure if this could indicate the root cause? The getuserinformationasync; and if that's trying to look at the id token, or if it's making a call to the userinfo side?
|
The scenario's causing the issue were mitigated slightly with extending the timeouts, but it appears to be related to retrieval of information from the /userinfo endpoint. Q1: Can we eliminate that call entirely, and lean on the information provided in the ID Token retrieved?
|
Describe the bug?
Intermittent failures are being returned to clients with 500. Re-initiating will return 302 as expected, and successfully log in.
What is expected to happen?
POST with state & code to /authorization-code/callback will return 302 and allow authentication/authorization.
What is the actual behavior?
Intermittent 500 application error returned, with no additional information available
Reproduction Steps?
Multiple internal apps (2) using ASP.NET Core Blazor experience intermittent issues.
Additional Information?
Cannot determine how to collect additional relevant logs in .net8 with startup class change. If there is an effective way to isolate & troubleshoot more, I would be happy to do that first & return more useful logs.
.NET Version
.net 8
Blazor app
SDK Version
Okta ASP.NET 4.6.1
OS version
No response
The text was updated successfully, but these errors were encountered: