#### [Abblix\.SecurityEvents](https://www.abblix.com/en/docs/api/abblix-securityevents 'index')
### [Abblix\.SecurityEvents\.BackChannelLogout](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.BackChannelLogout 'Abblix\.SecurityEvents\.BackChannelLogout')

## LogoutNotification Class

Which sessions a validated Logout Token says to end\.

```csharp
public sealed record LogoutNotification : System.IEquatable<Abblix.SecurityEvents.BackChannelLogout.LogoutNotification>
```

Inheritance [System\.Object](https://learn.microsoft.com/en-us/dotnet/api/system.object 'System\.Object') → LogoutNotification

Implements [System\.IEquatable&lt;](https://learn.microsoft.com/en-us/dotnet/api/system.iequatable-1 'System\.IEquatable\`1')[LogoutNotification](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.BackChannelLogout.LogoutNotification 'Abblix\.SecurityEvents\.BackChannelLogout\.LogoutNotification')[&gt;](https://learn.microsoft.com/en-us/dotnet/api/system.iequatable-1 'System\.IEquatable\`1')

### Remarks
What OpenID Connect Back\-Channel Logout 1\.0 Section 2\.7 asks the RP to act on: "locate the
session\(s\) identified by the iss and sub Claims and/or the sid Claim", then "clear any state
associated with the identified session\(s\)"\. Acting is the host's, since only the host knows
where its sessions are kept\.
### Constructors

## LogoutNotification\(string, string, string, string\) Constructor {#Abblix.SecurityEvents.BackChannelLogout.LogoutNotification.LogoutNotification(string,string,string,string)}

Which sessions a validated Logout Token says to end\.

```csharp
public LogoutNotification(string Issuer, string? Subject, string? SessionId, string? TokenId);
```
#### Parameters

###### `Issuer` [System\.String](https://learn.microsoft.com/en-us/dotnet/api/system.string 'System\.String') {#Abblix.SecurityEvents.BackChannelLogout.LogoutNotification.LogoutNotification(string,string,string,string).Issuer}

The provider that sent the notification\.

###### `Subject` [System\.String](https://learn.microsoft.com/en-us/dotnet/api/system.string 'System\.String') {#Abblix.SecurityEvents.BackChannelLogout.LogoutNotification.LogoutNotification(string,string,string,string).Subject}

The end\-user whose sessions are ending, when the token named one\. Every session this client
holds for that user at that issuer is meant, not one of them\.

###### `SessionId` [System\.String](https://learn.microsoft.com/en-us/dotnet/api/system.string 'System\.String') {#Abblix.SecurityEvents.BackChannelLogout.LogoutNotification.LogoutNotification(string,string,string,string).SessionId}

The single session that is ending, when the token named one\. Narrower than the subject, and the
two may arrive together\.

###### `TokenId` [System\.String](https://learn.microsoft.com/en-us/dotnet/api/system.string 'System\.String') {#Abblix.SecurityEvents.BackChannelLogout.LogoutNotification.LogoutNotification(string,string,string,string).TokenId}

The `jti` of the token that carried this notification\.

### Remarks
What OpenID Connect Back\-Channel Logout 1\.0 Section 2\.7 asks the RP to act on: "locate the
session\(s\) identified by the iss and sub Claims and/or the sid Claim", then "clear any state
associated with the identified session\(s\)"\. Acting is the host's, since only the host knows
where its sessions are kept\.
### Properties

## LogoutNotification\.Issuer Property {#Abblix.SecurityEvents.BackChannelLogout.LogoutNotification.Issuer}

The provider that sent the notification\.

```csharp
public string Issuer { get; init; }
```

#### Property Value
[System\.String](https://learn.microsoft.com/en-us/dotnet/api/system.string 'System\.String')

## LogoutNotification\.SessionId Property {#Abblix.SecurityEvents.BackChannelLogout.LogoutNotification.SessionId}

The single session that is ending, when the token named one\. Narrower than the subject, and the
two may arrive together\.

```csharp
public string? SessionId { get; init; }
```

#### Property Value
[System\.String](https://learn.microsoft.com/en-us/dotnet/api/system.string 'System\.String')

## LogoutNotification\.Subject Property {#Abblix.SecurityEvents.BackChannelLogout.LogoutNotification.Subject}

The end\-user whose sessions are ending, when the token named one\. Every session this client
holds for that user at that issuer is meant, not one of them\.

```csharp
public string? Subject { get; init; }
```

#### Property Value
[System\.String](https://learn.microsoft.com/en-us/dotnet/api/system.string 'System\.String')

## LogoutNotification\.TokenId Property {#Abblix.SecurityEvents.BackChannelLogout.LogoutNotification.TokenId}

The `jti` of the token that carried this notification\.

```csharp
public string? TokenId { get; init; }
```

#### Property Value
[System\.String](https://learn.microsoft.com/en-us/dotnet/api/system.string 'System\.String')
### Methods

## LogoutNotification\.Matches\(JsonWebToken\) Method {#Abblix.SecurityEvents.BackChannelLogout.LogoutNotification.Matches(Abblix.Jwt.JsonWebToken)}

Reports whether this notification is about the session [identityToken](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.BackChannelLogout.LogoutNotification#Abblix.SecurityEvents.BackChannelLogout.LogoutNotification.Matches(Abblix.Jwt.JsonWebToken).identityToken 'Abblix\.SecurityEvents\.BackChannelLogout\.LogoutNotification\.Matches\(Abblix\.Jwt\.JsonWebToken\)\.identityToken')
belongs to\.

```csharp
public bool Matches(Abblix.Jwt.JsonWebToken identityToken);
```
#### Parameters

###### `identityToken` [JsonWebToken](https://www.abblix.com/en/docs/api/abblix-jwt/Abblix.Jwt.JsonWebToken 'Abblix\.Jwt\.JsonWebToken') {#Abblix.SecurityEvents.BackChannelLogout.LogoutNotification.Matches(Abblix.Jwt.JsonWebToken).identityToken}

The ID Token of a session this client is holding, as validated when that session was
established\.

#### Returns
[System\.Boolean](https://learn.microsoft.com/en-us/dotnet/api/system.boolean 'System\.Boolean')  
`true` when the notification names that session and nothing contradicts it\.

### Remarks
Steps 9, 10 and 11 of OpenID Connect Back\-Channel Logout 1\.0 Section 2\.6, which the
specification introduces with "Optionally verify that the iss Logout Token Claim matches the
iss Claim in an ID Token issued for the current session or a recent session", and likewise
of any `sub` and any `sid`\.
They are offered here rather than performed during validation because they are questions
about a session, and only the host knows which sessions it holds \- Section 2\.7 already makes
it responsible for finding them\. What the library can do is make the comparison one call
rather than three hand\-written string comparisons, which is where a case\-insensitive or a
null\-tolerant one creeps in\.
Note what "matches" means for a claim the token did not carry: the notification names a
subject or a session or both, and a claim it did not name places no restriction\. A
notification carrying only a subject is about every session this client holds for that user,
which is exactly what a provider means by omitting the session identifier\.