Skip to content
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

LogOut: Still signed in after SignOutAsync! #6439

Closed
0x0041764C opened this issue May 16, 2018 — with docs.microsoft.com · 3 comments
Closed

LogOut: Still signed in after SignOutAsync! #6439

0x0041764C opened this issue May 16, 2018 — with docs.microsoft.com · 3 comments
Assignees
Labels
Source - Docs.ms Docs Customer feedback via GitHub Issue
Milestone

Comments

Copy link

0x0041764C commented May 16, 2018

After calling SignOutAsync I was still signed in. When returning 'void' (async Task) the problem was solved.
Fatal is, that it seems to work with Postman during testing. But in the app after LogOut I was still logged in with the same user. Even after logging in as a different user.

See https://stackoverflow.com/a/48460538/8405156

The problem is that your RedirectToAction overwrites the redirect to the Identity Server endsession URL that SignOutAsync issues.

I think the documentation should be updated to make aware that this is a problem.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@Rick-Anderson
Copy link
Contributor

@HaoK should I add this to the doc?

@Rick-Anderson Rick-Anderson self-assigned this May 16, 2018
@Rick-Anderson Rick-Anderson added the Source - Docs.ms Docs Customer feedback via GitHub Issue label May 16, 2018
@Rick-Anderson Rick-Anderson added this to the 2018 - Quarter 2 milestone May 16, 2018
@HaoK
Copy link
Member

HaoK commented May 16, 2018

Sure its reasonable to call out, basically don't redirect after a sign out call

Copy link

Am unable to Authorize the application using the role after successful authentication. Am returning The Role from the ADFS Claims provider. The message from asp.net core 2.1 application Access denied
You do not have access to this resource. Need this to work as its currently working on an MV5 application

@dotnet dotnet locked as resolved and limited conversation to collaborators Aug 28, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Source - Docs.ms Docs Customer feedback via GitHub Issue
Projects
None yet
Development

No branches or pull requests

4 participants