Skip to content

Commit

Permalink
Update external_notification.md
Browse files Browse the repository at this point in the history
*<iframe>* does not show on the page when rendered.
  • Loading branch information
DavidKlempfner authored Oct 2, 2023
1 parent a75c1de commit 082fbb7
Showing 1 changed file with 2 additions and 2 deletions.
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,8 @@ Federated sign-out is the situation where a user has used an external identity p
When the user signs out, it will be useful for IdentityServer to be notified so that it can sign the user out of IdentityServer and all of the applications that use IdentityServer.

Not all external identity providers support federated sign-out, but those that do will provide a mechanism to notify clients that the user has signed out.
This notification usually comes in the form of a request in an *<iframe>* from the external identity provider's "logged out" page.
IdentityServer must then notify all of its clients (as discussed [here]({{< ref "../logout" >}})), also typically in the form of a request in an *<iframe>* from within the external identity provider's *<iframe>*.
This notification usually comes in the form of a request in an *iframe* from the external identity provider's "logged out" page.
IdentityServer must then notify all of its clients (as discussed [here]({{< ref "../logout" >}})), also typically in the form of a request in an *iframe* from within the external identity provider's *<iframe>*.

What makes federated sign-out a special case (when compared to a normal [logout]({{< ref "../logout" >}})) is that the federated sign-out request is not to the normal sign-out endpoint in IdentityServer.
In fact, each external IdentityProvider will have a different endpoint into your IdentityServer host.
Expand Down

0 comments on commit 082fbb7

Please sign in to comment.