Diese Seite wurde noch nicht übersetzt.

Abblix.Jwt.Signing Namespace

Interfaces

IDataSigner A signing backend that owns a slice of the server's signing keys and produces JWS signature bytes for the keys it owns. Backends compose as peers behind Abblix.Jwt.Signing.CompositeSigner, which asks each in turn whether it owns the key (CanSign(JsonWebKey)) and routes to the first that does: the in-process Abblix.Jwt.Signing.LocalKeySigner owns keys that carry private material, an external custodian backend (Abblix.Jwt.ExternalKeys.ExternalKeySigner) owns the public-only keys whose kid is its handle. This is the byte-level counterpart of the token-level IJsonWebTokenSigner: it works with bytes, not a whole token, so an HSM/KMS/vault integration is one more backend and never touches JWS framing.

ISignatureAlgorithm<TJsonWebKey> Defines the contract for signing and verifying JWT tokens using a specific cryptographic algorithm.

Interfaces
IDataSigner	A signing backend that owns a slice of the server's signing keys and produces JWS signature bytes for the keys it owns. Backends compose as peers behind Abblix.Jwt.Signing.CompositeSigner, which asks each in turn whether it owns the key (CanSign(JsonWebKey)) and routes to the first that does: the in-process Abblix.Jwt.Signing.LocalKeySigner owns keys that carry private material, an external custodian backend (Abblix.Jwt.ExternalKeys.ExternalKeySigner) owns the public-only keys whose `kid` is its handle. This is the byte-level counterpart of the token-level IJsonWebTokenSigner: it works with bytes, not a whole token, so an HSM/KMS/vault integration is one more backend and never touches JWS framing.
ISignatureAlgorithm<TJsonWebKey>	Defines the contract for signing and verifying JWT tokens using a specific cryptographic algorithm.