BackChannelLogoutValidationOptions Class

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.

public sealed record BackChannelLogoutValidationOptions : Abblix.SecurityEvents.Validation.SecurityEventTokenValidationOptions, System.IEquatable<Abblix.SecurityEvents.BackChannelLogout.BackChannelLogoutValidationOptions>

Inheritance System.Object → SecurityEventTokenValidationOptions → BackChannelLogoutValidationOptions

Implements System.IEquatable<BackChannelLogoutValidationOptions>

Remarks

It adds no member to the base, and exists for the one thing a base type cannot supply: its own identity in the container. A host running this receiver beside a Shared Signals one holds two sets of expectations that are the same shape and must never be swapped - the audience here is this client, there it is the stream's receiver - and a single registration of the base type would let whichever ran last answer for both.