| BackChannelLogoutError | How an RP tells a provider that a logout request was bad: the optional body of the 400 response (OpenID Connect Back-Channel Logout 1.0 Section 2.8). |
| BackChannelLogoutError.ParameterNames | The wire names of the error members (RFC 6749 Section 5.2, by the reference in OpenID Connect Back-Channel Logout 1.0 Section 2.8). |
| BackChannelLogoutHandler | Takes one back-channel logout request from the transport and answers it: reads the logout_token out of the posted form, puts it through the receiver's profile, hands the notification to the application, and shapes the response (OpenID Connect Back-Channel Logout 1.0 Sections 2.5 and 2.8). |
| BackChannelLogoutResult | What a back-channel logout request earns: the status code the transport answers with, and - only beside a 400 - the error body the provider reads (OpenID Connect Back-Channel Logout 1.0 Section 2.8). The shape is transport-neutral on purpose: any host adapter renders it, none decides it. |
| BackChannelLogoutValidationOptions | What a back-channel logout receiver expects of every Logout Token: the provider it talks to as the issuer, its own client identifier as the audience, and the clock tolerance it allows. |
| LogoutNotification | Which sessions a validated Logout Token says to end. |
| LogoutTokenClaims | The part of a Logout Token that only its own specification defines, named as on the wire. |
| LogoutTokenValidationException | Thrown when a Logout Token failed one of the validation steps of section 2.6. |
| LogoutTokenValidator | Validates Logout Tokens arriving at this receiver's back-channel logout endpoint. |