| 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 | 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 | What Shared Signals adds to key resolution: the "jwks_uri" a transmitter advertises about itself. |
| PollClientExtensions | Polls a stream by its delivery configuration rather than by a bare URL. |
| 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 | 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 | 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 | Builds a management client for one transmitter, over the transport a host configures. |
| 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 | 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 | The HTTP transport a receiver reads a transmitter's configuration metadata over (SSF 1.0 Sections 7.2, 7.2.1). |