update:clients
scope.
backchannel_logout_initiators
object supports the following properties:
Property | Type | Required? | Description | Supported values |
---|---|---|---|---|
mode | string | Required | Configuration method for enabling initiators. | custom , all |
selected_initiators | array | Required if mode is custom | List of initiators to enable. | rp-logout , idp-logout , password-changed , session-expired , session-revoked , account-deleted , email-identifier-changed |
mode
property determines the configuration method for enabling initiators.
By default, it is set to custom
, which allows you to specify which initiators you want to enable. If you want your application to logout anytime the IdP session ends, set it to all
.
The mode
property supports the following values:
Value | Description |
---|---|
custom | Enables only the initiators listed in the selected_initiators array. |
all | Automatically enables all current and future initiators. |
selected_initiators
property contains the list of initiators to be enabled for the given application.
The selected_initiators
property supports the following values:
Value | Description |
---|---|
rp-logout | Request was initiated by a relying party (RP). |
idp-logout | Request was initiated by an external identity provider (IdP). |
password-changed | Request was initiated by a password change. |
session-expired | Request was initiated by session expiration. |
session-revoked | Request was initiated by session deletion. |
account-deleted | Request was initiated by an account deletion. |
email-identifier-changed | Request was initiated by an email identifier change. |
rp-logout
and idp-logout
) will be subscribed to by default. Any additional initiators, including any added in the future, must first be selected before they can initiate a logout from your application.
Select this option if you want your application to log out only for initiators you select.