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

## Abblix\.SecurityEvents\.Subjects Namespace

| Classes | |
| :--- | :--- |
| [AccountSubject](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.Subjects.AccountSubject 'Abblix\.SecurityEvents\.Subjects\.AccountSubject') | Identifies a subject by an account at a service provider, expressed as an "acct" URI \(RFC 9493 Section 3\.2\.1, RFC 7565\)\. |
| [AliasesSubject](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.Subjects.AliasesSubject 'Abblix\.SecurityEvents\.Subjects\.AliasesSubject') | 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\. |
| [ComplexSubject](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.Subjects.ComplexSubject 'Abblix\.SecurityEvents\.Subjects\.ComplexSubject') | A Complex Subject: several Simple Subject Members \- a user, the device they are on, the session they hold \- that all describe attributes of, and together refer to, exactly one Subject Principal \(SSF 1\.0 Sections 3\.3, 3\.3\.1\)\. |
| [DidSubject](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.Subjects.DidSubject 'Abblix\.SecurityEvents\.Subjects\.DidSubject') | Identifies a subject by a Decentralized Identifier URL \(RFC 9493 Section 3\.2\.6\)\. |
| [EmailCanonicalization](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.Subjects.EmailCanonicalization 'Abblix\.SecurityEvents\.Subjects\.EmailCanonicalization') | The one email transformation RFC 9493 settles, offered for comparing addresses rather than for storing them\. |
| [EmailSubject](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.Subjects.EmailSubject 'Abblix\.SecurityEvents\.Subjects\.EmailSubject') | Identifies a subject by an email address \(RFC 9493 Section 3\.2\.2\)\. |
| [IpAddressesSubject](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.Subjects.IpAddressesSubject 'Abblix\.SecurityEvents\.Subjects\.IpAddressesSubject') | Identifies a subject by the IP addresses the transmitter observed for it \(SSF 1\.0 Section 3\.5\.3\), each in the RFC 4001 textual representation\. |
| [IssSubSubject](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.Subjects.IssSubSubject 'Abblix\.SecurityEvents\.Subjects\.IssSubSubject') | Identifies a subject by a pair of issuer and subject values, the way an OpenID Connect ID token identifies its subject through the "iss" and "sub" claims \(RFC 9493 Section 3\.2\.3\)\. |
| [JwtIdSubject](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.Subjects.JwtIdSubject 'Abblix\.SecurityEvents\.Subjects\.JwtIdSubject') | Identifies a subject that is itself a JWT, by the issuer that minted it and its token identifier \(SSF 1\.0 Section 3\.5\.1\) \- the shape a CAEP token\-revocation event names its victim in\. |
| [OpaqueSubject](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.Subjects.OpaqueSubject 'Abblix\.SecurityEvents\.Subjects\.OpaqueSubject') | Identifies a subject by a string that asserts nothing beyond being its identifier, such as a UUID or a surrogate key for a database record \(RFC 9493 Section 3\.2\.4\)\. |
| [PhoneNumberCanonicalization](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.Subjects.PhoneNumberCanonicalization 'Abblix\.SecurityEvents\.Subjects\.PhoneNumberCanonicalization') | Removes presentation characters from a telephone number so that two senders' spellings of one number can be compared\. |
| [PhoneNumberSubject](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.Subjects.PhoneNumberSubject 'Abblix\.SecurityEvents\.Subjects\.PhoneNumberSubject') | Identifies a subject by a telephone number \(RFC 9493 Section 3\.2\.5\)\. |
| [SamlAssertionIdSubject](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.Subjects.SamlAssertionIdSubject 'Abblix\.SecurityEvents\.Subjects\.SamlAssertionIdSubject') | Identifies a subject that is a SAML 2\.0 assertion, by the assertion's Issuer and ID values \(SSF 1\.0 Section 3\.5\.2\)\. Note the member names differ from the jwt\_id format's: the full words "issuer" and "assertion\_id", not the JWT claim abbreviations\. |
| [SubjectFormats](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.Subjects.SubjectFormats 'Abblix\.SecurityEvents\.Subjects\.SubjectFormats') | Values for the Subject Identifier "format" member \(RFC 9493 Section 3\), naming the set of rules by which a subject is encoded; the discriminator when deserializing a [SubjectIdentifier](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.Subjects.SubjectIdentifier 'Abblix\.SecurityEvents\.Subjects\.SubjectIdentifier') into the correct concrete subtype\. Two families live here, each constant naming its own: the formats of the IANA "Security Event Subject Identifier Formats" registry \(RFC 9493 Section 8\.1\.2\), and the extensions OpenID Shared Signals Framework 1\.0 defines on top of that registry \(SSF 1\.0 Sections 3\.3, 3\.5\) \- which its Section 11 asks IANA to register, a registration the registry does not yet show\. |
| [SubjectIdentifier](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.Subjects.SubjectIdentifier 'Abblix\.SecurityEvents\.Subjects\.SubjectIdentifier') | A Subject Identifier: a JSON object whose contents identify a subject within some context \(RFC 9493 Section 3\)\. |
| [SubjectIdentifierJsonConverter](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.Subjects.SubjectIdentifierJsonConverter 'Abblix\.SecurityEvents\.Subjects\.SubjectIdentifierJsonConverter') | Reads and writes a [SubjectIdentifier](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.Subjects.SubjectIdentifier 'Abblix\.SecurityEvents\.Subjects\.SubjectIdentifier') polymorphically, choosing the concrete subtype by the "format" member that RFC 9493 Section 3 requires every Subject Identifier to carry\. |
| [SubjectMemberNames](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.Subjects.SubjectMemberNames 'Abblix\.SecurityEvents\.Subjects\.SubjectMemberNames') | Names of the JSON members a Subject Identifier may carry\. A member name is shared with whoever reads the identifier on the other side, so it is single\-sourced here rather than repeated as a literal at each declaration\. Each constant names its origin: the RFC 9493 formats \(Section 3\.2\) or the OpenID Shared Signals Framework 1\.0 extensions \(Sections 3\.3, 3\.5\)\. |
| [UriSubject](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.Subjects.UriSubject 'Abblix\.SecurityEvents\.Subjects\.UriSubject') | Identifies a subject by a URI \(RFC 9493 Section 3\.2\.7, RFC 3986\)\. |