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

## Abblix\.SharedSignals\.Receiver\.SecurityEvent Namespace

| Classes | |
| :--- | :--- |
| [CriticalSubjectMembersStep](https://www.abblix.com/en/docs/api/abblix-sharedsignals/Abblix.SharedSignals.Receiver.SecurityEvent.CriticalSubjectMembersStep 'Abblix\.SharedSignals\.Receiver\.SecurityEvent\.CriticalSubjectMembersStep') | Enforces the receiver half of subject processing \(SSF 1\.0 Section 3\.6\): an event whose subject carries a critical member this receiver cannot interpret is discarded, never processed with the member silently dropped \- acting on a subject while blind to a member the transmitter declared essential could act on the wrong principal\. |
| [ForbidSubStep](https://www.abblix.com/en/docs/api/abblix-sharedsignals/Abblix.SharedSignals.Receiver.SecurityEvent.ForbidSubStep 'Abblix\.SharedSignals\.Receiver\.SecurityEvent\.ForbidSubStep') | Requires the claims to carry no "sub": SSF identifies the subject through the structured top\-level "sub\_id" alone, and "The JWT 'sub' claim MUST NOT be present in any SET containing an SSF event" \(SSF 1\.0 Section 4\.1\.2\) \- one of the restrictions Section 4\.1\.3 adds to keep SSF SETs from being confused with other kinds of JWTs\. |
| [JwksKeyResolutionOptionsExtensions](https://www.abblix.com/en/docs/api/abblix-sharedsignals/Abblix.SharedSignals.Receiver.SecurityEvent.JwksKeyResolutionOptionsExtensions 'Abblix\.SharedSignals\.Receiver\.SecurityEvent\.JwksKeyResolutionOptionsExtensions') | What Shared Signals adds to key resolution: the "jwks\_uri" a transmitter advertises about itself\. |
| [PollClientExtensions](https://www.abblix.com/en/docs/api/abblix-sharedsignals/Abblix.SharedSignals.Receiver.SecurityEvent.PollClientExtensions 'Abblix\.SharedSignals\.Receiver\.SecurityEvent\.PollClientExtensions') | Polls a stream by its delivery configuration rather than by a bare URL\. |
| [SharedSignalsValidationOptions](https://www.abblix.com/en/docs/api/abblix-sharedsignals/Abblix.SharedSignals.Receiver.SecurityEvent.SharedSignalsValidationOptions 'Abblix\.SharedSignals\.Receiver\.SecurityEvent\.SharedSignalsValidationOptions') | The validation expectations of an SSF receiver: everything the core profile expects of a SET, plus what the SSF profile adds \- the stream the event must belong to and the transmitter's declared critical subject members\. The SSF steps refuse to run against the base options type, so a profile wired with the wrong flavor fails loudly on its first token\. |
| [StreamIssuerStep](https://www.abblix.com/en/docs/api/abblix-sharedsignals/Abblix.SharedSignals.Receiver.SecurityEvent.StreamIssuerStep 'Abblix\.SharedSignals\.Receiver\.SecurityEvent\.StreamIssuerStep') | Binds each event to the stream it arrived on: the "iss" claim must equal the Stream Configuration's issuer \(SSF 1\.0 Section 4\.1\.6\)\. Without this binding a token from any trusted issuer would be accepted on any stream, and events could be replayed across streams whose issuers differ\. |
| [StreamManagementClient](https://www.abblix.com/en/docs/api/abblix-sharedsignals/Abblix.SharedSignals.Receiver.SecurityEvent.StreamManagementClient 'Abblix\.SharedSignals\.Receiver\.SecurityEvent\.StreamManagementClient') | The receiver's side of the Event Stream Management API of one transmitter \(SSF 1\.0 Section 8\.1\): stream lifecycle, status, subjects and verification, each method speaking to the endpoint the transmitter's configuration metadata advertises\. |
| [StreamManagementClientFactory](https://www.abblix.com/en/docs/api/abblix-sharedsignals/Abblix.SharedSignals.Receiver.SecurityEvent.StreamManagementClientFactory 'Abblix\.SharedSignals\.Receiver\.SecurityEvent\.StreamManagementClientFactory') | Builds a management client for one transmitter, over the transport a host configures\. |
| [StreamManagementTransport](https://www.abblix.com/en/docs/api/abblix-sharedsignals/Abblix.SharedSignals.Receiver.SecurityEvent.StreamManagementTransport 'Abblix\.SharedSignals\.Receiver\.SecurityEvent\.StreamManagementTransport') | The HTTP transport a receiver manages its streams over: the Event Stream Management API of one transmitter \(SSF 1\.0 Section 8\.1\)\. |
| [TransmitterConfigurationClient](https://www.abblix.com/en/docs/api/abblix-sharedsignals/Abblix.SharedSignals.Receiver.SecurityEvent.TransmitterConfigurationClient 'Abblix\.SharedSignals\.Receiver\.SecurityEvent\.TransmitterConfigurationClient') | Fetches a transmitter's configuration metadata from the well\-known address its issuer identifier resolves to \(SSF 1\.0 Sections 7\.2, 7\.2\.1\), and refuses a document that does not assert the issuer it was fetched for\. |
| [TransmitterConfigurationTransport](https://www.abblix.com/en/docs/api/abblix-sharedsignals/Abblix.SharedSignals.Receiver.SecurityEvent.TransmitterConfigurationTransport 'Abblix\.SharedSignals\.Receiver\.SecurityEvent\.TransmitterConfigurationTransport') | The HTTP transport a receiver reads a transmitter's configuration metadata over \(SSF 1\.0 Sections 7\.2, 7\.2\.1\)\. |