-
Notifications
You must be signed in to change notification settings - Fork 0
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
id_token_hint missing on signout with Dynamic Identity Providers #958
Comments
Are you using Asp.Net Identity in your application? Do you know what the |
@AndersAbel Yes I am using Asp.Net Identity. The SignOutScheme is |
If you are using Asp.Net Identity the default scheme is changed to |
@AndersAbel that worked, thank you so much! Is this mentioned in your documentation anywhere? If so I'd like to reference it in our internal Knowledge Base. |
No, it's not explicitly documented. But it's a good idea as this is a common source of confusion. I've added it to my backlog: DuendeSoftware/docs.duendesoftware.com#367 |
Thank you again! I've thoroughly tested it, and it seems to be working great! |
Which version of Duende IdentityServer are you using?
6.3.5
Which version of .NET are you using?
net6.0
Describe the bug
When signing out of a dynamic identity provider from the AspNetCore MVC UI from the Duende IdentityServer 6 EntityFrameworkCore template, the id_token_hint query parameter is missing.
If I call
HttpContext.GetTokenAsync("id_token")
from/Pages/Account/Logout/Index.cshtml.cs
it returns the id_token, but when placing a breakpoint in the OpenIdConnectHandler where the IdTokenHint should be added to the request (OpenIdConnectHandler.cs Ln 247), the id_token is null.To Reproduce
Expected behavior
Should be redirected to the Identity Provider with an
id_token_hint
query parameter.A clear and concise description of what you expected to happen.
Log output/exception with stacktrace
Additional context
I am trying to integrate with Okta as an Identity Provider which requires id_token_hint when logging out.
The text was updated successfully, but these errors were encountered: