You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Implement OpenID Connect Front-Channel Logout 1.0 specification:
- Add default /front_channel_logout location that handles logout requests
- Both sid and iss parameters must be present
- Issuer verification against iss claim in ID token
Reference: https://openid.net/specs/openid-connect-frontchannel-1_0.html
Copy file name to clipboardExpand all lines: README.md
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -100,6 +100,10 @@ Requests made to the `/logout` location invalidate both the ID token, access tok
100
100
101
101
RP-initiated logout is supported according to [OpenID Connect RP-Initiated Logout 1.0](https://openid.net/specs/openid-connect-rpinitiated-1_0.html). This behavior is controlled by the `$oidc_end_session_endpoint` variable.
102
102
103
+
#### Front-Channel OIDC Logout
104
+
105
+
Front-Channel Logout is supported according to [OpenID Connect Front-Channel Logout 1.0](https://openid.net/specs/openid-connect-frontchannel-1_0.html). The `/front_channel_logout endpoint` location handles logout requests from the IdP. Both arguments, `sid` (session identifier) and `iss` (issuer identifier), must be present.
106
+
103
107
### Multiple IdPs
104
108
105
109
Where NGINX Plus is configured to proxy requests for multiple websites or applications, or user groups, these may require authentication by different IdPs. Separate IdPs can be configured, with each one matching on an attribute of the HTTP request, e.g. hostname or part of the URI path.
@@ -198,6 +202,7 @@ The key-value store is used to maintain persistent storage for ID tokens and ref
0 commit comments