LogoutEventStep Class
Requires the events claim to name the back-channel logout event - step 6 of OpenID
Connect Back-Channel Logout 1.0 Section 2.6.
public sealed class LogoutEventStep : Abblix.SecurityEvents.Validation.ISecurityEventTokenValidatorInheritance System.Object → LogoutEventStep
Implements ISecurityEventTokenValidator
Remarks
This is what makes the token a logout order rather than some other event the same issuer signed for the same audience. Without it any such token would be accepted here and end a session, which is the cross-JWT confusion Section 4.1 names.
The step above requires the claim to exist at all; this one requires what it says. The two are separate because the profile inherits the first from the security-event defaults, where every SET carries events, and only the member name is particular to logout.
Methods
LogoutEventStep.ValidateAsync(SecurityEventTokenValidationContext, CancellationToken) Method
Checks the token in flight.
public System.Threading.Tasks.ValueTask<Abblix.SecurityEvents.Validation.SecurityEventTokenValidationError?> ValidateAsync(Abblix.SecurityEvents.Validation.SecurityEventTokenValidationContext context, System.Threading.CancellationToken cancellationToken);Parameters
context SecurityEventTokenValidationContext
The state accumulated by earlier steps.
cancellationToken System.Threading.CancellationToken
Cancels I/O the step performs, such as key retrieval.
Implements ValidateAsync(SecurityEventTokenValidationContext, CancellationToken)
Returns
System.Threading.Tasks.ValueTask<SecurityEventTokenValidationError>
Null to pass the token on; an error to stop the pipeline with that verdict.