Abblix.SecurityEvents.Infrastructure Namespace
| Classes | |
|---|---|
| DefaultSecurityEventTokenSigner | The out-of-the-box signer: compact JWS through the Abblix JWT core, with the signing key from the source the host configured. |
| DefaultSecurityEventTokenVerifier | The out-of-the-box verifier: signature verification through the Abblix JWT core, with keys from the issuer resolver. |
| JwksIssuerKeyResolver | Resolves issuers' verification keys from their published JWK Set documents, cached so the hot path of validation performs no network I/O. |
| JwksKeyResolutionOptions | How JWKS-based key resolution finds and refreshes issuers' keys. |
| JwksTransport | The HTTP transport key-set fetches travel on, to the "jwks_uri" of an issuer whose events this host verifies. |
| SecurityEventsOptions | What a host configures once about its security-event handling: the event dictionary, signing, and - for a profile that weakens the default validation - the reasoned acknowledgement of that weakening. The pipeline itself is composed through the service collection: the default steps register as an ordinary family, and a consumer profile edits them in place through the live composition cursor after AddSecurityEvents. |
| ServiceCollectionExtensions | Wires the package into a host's service collection. Every registration lets a host pre-registration win: the extension supplies defaults, never overrides. |
| ValidationProfile | One named validation profile under construction: the editing surface AddSecurityEventValidationProfile(this IServiceCollection, object, Action<ValidationProfile>) hands to its configure delegate. |
| ValidationProfileKeys | Names the validation profiles built over this core: each a keyed ISecurityEventTokenValidator family that one consumer creates, edits and resolves, so what one demands of its own kind of token never collides with what another demands of its. |