AliasesSubject Class

Identifies a subject by several Subject Identifiers at once, each naming the same entity (RFC 9493 Section 3.2.8). It is meant for the case where a transmitter has shared a variety of identifiers with a receiver and does not know which of them the receiver will recognise.

public sealed class AliasesSubject : Abblix.SecurityEvents.Subjects.SubjectIdentifier

Inheritance System.Object → SubjectIdentifier → AliasesSubject

Remarks

Presenting several identifiers together tells the receiver that they belong to one subject, which is information in its own right. RFC 9493 Section 6.1 asks a transmitter to send them together only where the receiver already knows they are related, or where the correlation is what the use case is about.

Constructors

AliasesSubject(SubjectIdentifier[]) Constructor

Creates an Aliases Subject Identifier from the identifiers given.

public AliasesSubject(params Abblix.SecurityEvents.Subjects.SubjectIdentifier[] identifiers);

Parameters

identifiers SubjectIdentifier[]

The Subject Identifiers naming the subject, under the same conditions as the primary constructor.

AliasesSubject(IReadOnlyList<SubjectIdentifier>) Constructor

Creates an Aliases Subject Identifier.

public AliasesSubject(System.Collections.Generic.IReadOnlyList<Abblix.SecurityEvents.Subjects.SubjectIdentifier> identifiers);

Parameters

identifiers System.Collections.Generic.IReadOnlyList<SubjectIdentifier>

The Subject Identifiers naming the subject. REQUIRED, must hold at least one entry, and must hold no Aliases Subject Identifier of its own.

Exceptions

System.ArgumentNullException
identifiers is null.

System.ArgumentException
identifiers is empty, holds a null entry, or holds a nested AliasesSubject.

Properties

AliasesSubject.Identifiers Property

The Subject Identifiers naming the subject, each identifying the same entity.

public System.Collections.Generic.IReadOnlyList<Abblix.SecurityEvents.Subjects.SubjectIdentifier> Identifiers { get; }

Property Value

System.Collections.Generic.IReadOnlyList<SubjectIdentifier>

Remarks

The same Identifier Format may appear more than once, which is how a subject with two email addresses is expressed. RFC 9493 Section 3.2.8 says exact duplicates SHOULD NOT appear; that is a SHOULD NOT rather than a MUST NOT, so a duplicate is left to the caller and never silently dropped here.