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

Fixes wording error #377

Merged
merged 2 commits into from
Nov 28, 2023
Merged

Fixes wording error #377

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
41ac826
Update logout_context.md
Ranj101 Nov 15, 2023
d471980
Make same fixes in v6, v7
josephdecock Nov 28, 2023
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/v5/docs/content/ui/logout/logout_context.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ The logout page can be triggered in different ways:
* External Provider Logout Notification (protocol)
* Direct User Access (non-protocol)

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.
If the logout 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.

Expand Down
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 @@ -13,7 +13,7 @@ The logout page can be triggered in different ways:
* External Provider Logout Notification (protocol)
* Direct User Access (non-protocol)

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.
If the logout 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">}}) to obtain a *LogoutRequest* object.

Expand Down
2 changes: 1 addition & 1 deletion IdentityServer/v7/docs/content/ui/logout/logout_context.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ The logout page can be triggered in different ways:
* External Provider Logout Notification (protocol)
* Direct User Access (non-protocol)

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.
If the logout 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">}}) to obtain a *LogoutRequest* object.

Expand Down
Loading