-
Notifications
You must be signed in to change notification settings - Fork 10.3k
NavigationManager.NavigateToLogout() stuck on authentication/logout-callback - reopen. #57202
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
Comments
I was not able to respond promptly to 57632. I didn't see an option to reopen 57632 so attaching the requested debug output here. |
When I run in localhost, the front end logs out normally. Would you like the same debug out from localhost to compare with the log output i've attached from our test environment? |
Any updates? |
Any new updates? |
The comment "added to 9.0-rc2" |
Thanks for the debug logs. I am able to verify that I can publish and trim a Blazor WebAssembly app using However, I was able to reproduce something similar to your logs which abruptly end after handing Your failed logs
Successful logs
Failed logs after revisiting logout-callback?state=...
In my case, this happens because the state url was cleared from local storage here when the state was read the first time the logout-callback was processed. You'll notice I have an extra trace-level log for If that doesn't give you enough information to resolve the issue on your own, we'll need a minimal repro that demonstrates the problem. You can omit the "Authority" and "ClientId" for the OIDC configuration, but it should otherwise be complete. |
Thank you for filing this issue. In order for us to investigate this issue, please provide a minimal repro project that illustrates the problem without unnecessary code. Please share with us in a public GitHub repo because we cannot open ZIP attachments, and don't include any confidential content. |
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate. See our Issue Management Policies for more information. |
Is there an existing issue for this?
Describe the bug
This is to reopen task 56732
Expected Behavior
Please reference 56732
Steps To Reproduce
Please reference 56732
Exceptions (if any)
No response
.NET Version
8.x
Anything else?
Here is the debug output requested on
56732
Debugoutput.zip
The text was updated successfully, but these errors were encountered: