Skip to content

NavigationManager.NavigateToLogout() stuck on authentication/logout-callback #56732

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

Closed
1 task done
dean-azure opened this issue Jul 10, 2024 · 7 comments
Closed
1 task done
Labels
area-blazor Includes: Blazor, Razor Components Needs: Author Feedback The author of this issue needs to respond in order for us to continue investigating this issue.

Comments

@dean-azure
Copy link

dean-azure commented Jul 10, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

This task #53131

Is marked as closed but I am still experiencing a very similr issue.

In our deployed environments when the user logs out it navigates to /authentication/logout-callback

Displays:
Processing logout callback...

But I cannot replicate this locally. So when I run in localhost the logout works as expected. But, I cannot diagnose what the problem is locally since the deployed version has different behavior

Our project has the 8.x Microsoft.AspNetCore.Components.WebAssembly.Authentication library the service is configured to use .net 8

The problem persists.

Additionally, I looked at the session values, the user remains logged in.

Expected Behavior

The user should be fully logged out

Steps To Reproduce

Already described above

Exceptions (if any)

No response

.NET Version

8.0

Anything else?

No response

@dotnet-issue-labeler dotnet-issue-labeler bot added the area-blazor Includes: Blazor, Razor Components label Jul 10, 2024
@javiercn
Copy link
Member

@dean-azure thanks for contacting us.

Can you provide more details?

  • What auth provider are you trying to use.
  • Are there any errors on the developer console? (F12).
  • Have you turned logging to Debug level on the client?
    • That will produce a detailed log of every operation the client is doing.

@javiercn javiercn added the Needs: Author Feedback The author of this issue needs to respond in order for us to continue investigating this issue. label Jul 11, 2024
@dean-azure
Copy link
Author

Our provider is OKTA

No errors are logged in the console.

beta.commoditysolutions.stonex.com-1721069751141.log

I've attached a the debug log output from edge in debug mode.

@dotnet-policy-service dotnet-policy-service bot added Needs: Attention 👋 This issue needs the attention of a contributor, typically because the OP has provided an update. and removed Needs: Author Feedback The author of this issue needs to respond in order for us to continue investigating this issue. labels Jul 15, 2024
@javiercn
Copy link
Member

@dean-azure thanks for the additional details.

Unfortunately, we don't think you've setup the login level to debug correctly. There should be way more logs appearing on the console if that were the case. Ensure you set the log level for Microsoft.AspNetCore.Components.WebAssembly.Authentication to debug.

What might have happened is that the directive for Microsoft.AspNetCore has overridden the log level you might have setup. If for some reason setting it up in config doesn't work, set it on Program.cs too

You should see logs that have [Microsoft.AspNetCore.Components.WebAssembly.Authentication] in the console when things are correctly setup.

@javiercn javiercn added Needs: Author Feedback The author of this issue needs to respond in order for us to continue investigating this issue. and removed Needs: Attention 👋 This issue needs the attention of a contributor, typically because the OP has provided an update. labels Jul 16, 2024
@dean-azure
Copy link
Author

"Ensure you set the log level for Microsoft.AspNetCore.Components.WebAssembly.Authentication to debug."

Where/how do I set this?

@dotnet-policy-service dotnet-policy-service bot added Needs: Attention 👋 This issue needs the attention of a contributor, typically because the OP has provided an update. and removed Needs: Author Feedback The author of this issue needs to respond in order for us to continue investigating this issue. labels Jul 18, 2024
@javiercn javiercn added Needs: Author Feedback The author of this issue needs to respond in order for us to continue investigating this issue. and removed Needs: Attention 👋 This issue needs the attention of a contributor, typically because the OP has provided an update. labels Jul 22, 2024
@dean-azure
Copy link
Author

@dean-azure here is a sample

https://learn.microsoft.com/en-us/aspnet/core/blazor/fundamentals/logging?view=aspnetcore-8.0#client-side-authentication-logging

Sorry, this I know how to do. I thought you were referring to a browser setting. I can do this later. Setting logging to debug brings the UI to a halt practically so I have to schedule. Will get it back to you within the next day or so.

@dotnet-policy-service dotnet-policy-service bot added Needs: Attention 👋 This issue needs the attention of a contributor, typically because the OP has provided an update. and removed Needs: Author Feedback The author of this issue needs to respond in order for us to continue investigating this issue. labels Jul 23, 2024
@mkArtakMSFT mkArtakMSFT added Needs: Author Feedback The author of this issue needs to respond in order for us to continue investigating this issue. and removed Needs: Attention 👋 This issue needs the attention of a contributor, typically because the OP has provided an update. labels Jul 24, 2024
@dean-azure
Copy link
Author

Sorry for the delay in getting this to you other production issues have kept me busy recently. :D

Debugoutput.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-blazor Includes: Blazor, Razor Components Needs: Author Feedback The author of this issue needs to respond in order for us to continue investigating this issue.
Projects
None yet
Development

No branches or pull requests

3 participants