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

## AccountSubject Class

Identifies a subject by an account at a service provider, expressed as an "acct" URI
\(RFC 9493 Section 3\.2\.1, RFC 7565\)\.

```csharp
public sealed class AccountSubject : Abblix.SecurityEvents.Subjects.SubjectIdentifier
```

Inheritance [System\.Object](https://learn.microsoft.com/en-us/dotnet/api/system.object 'System\.Object') → [SubjectIdentifier](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.Subjects.SubjectIdentifier 'Abblix\.SecurityEvents\.Subjects\.SubjectIdentifier') → AccountSubject
### Constructors

## AccountSubject\(string\) Constructor {#Abblix.SecurityEvents.Subjects.AccountSubject.AccountSubject(string)}

Identifies a subject by an account at a service provider, expressed as an "acct" URI
\(RFC 9493 Section 3\.2\.1, RFC 7565\)\.

```csharp
public AccountSubject(string uri);
```
#### Parameters

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

The "acct" URI of the subject's account\. REQUIRED, and must be neither null nor empty\.
### Properties

## AccountSubject\.Uri Property {#Abblix.SecurityEvents.Subjects.AccountSubject.Uri}

The "acct" URI identifying the account \(RFC 7565\)\.

```csharp
public string Uri { get; }
```

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

### Remarks
The value is carried as written, and that leniency is the decision taken: RFC 9493
Section 3\.2\.1 requires the value to be the subject's "acct" URI, but this type does not
verify the scheme, for the same reason [EmailSubject](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.Subjects.EmailSubject 'Abblix\.SecurityEvents\.Subjects\.EmailSubject') does not parse addr\-spec
and [PhoneNumberSubject](https://www.abblix.com/en/docs/api/abblix-securityevents/Abblix.SecurityEvents.Subjects.PhoneNumberSubject 'Abblix\.SecurityEvents\.Subjects\.PhoneNumberSubject') does not enforce E\.164 \- a receiver that discarded an
event over a malformed value would lose a signal it could still act on, so lexical
validation is left to the application that chooses to refuse\. No canonicalisation is stated
by the RFC either, so two spellings of one account remain two distinct identifiers here\.