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.

Sign up for GitHub

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

Update logout_context.md #349

Merged
merged 1 commit into from
Oct 3, 2023
Merged

Update logout_context.md #349

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion IdentityServer/v6/docs/content/ui/logout/logout_context.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ The logout page can be triggered in different ways:

If the login page is being triggered by a protocol workflow, then this means Duende IdentityServer has redirected the user's browser to the logout page.
In these scenarios, a *logoutId* parameter will be passed that represents the logout context.
The *logoutId* value can be exchanged with the *GetLogoutContextAsync* API on the [interaction service]({{<ref "/reference/services/interaction_service">}}) obtain a *LogoutRequest* object.
The *logoutId* value can be exchanged with the *GetLogoutContextAsync* API on the [interaction service]({{<ref "/reference/services/interaction_service">}}) to obtain a *LogoutRequest* object.

If the page is directly accessed by the user then there will be no *logoutId* parameter, but the context can still be accessed by calling *GetLogoutContextAsync* just without passing any parameters.

Expand Down
Loading