Staticacceptthe surface
the surface's name for it
the cause, or null where it may
StaticacceptWhy the ambient realm may not accept an X.509 signature, from what the certificate says. RSASSA-PSS's OID names no hash, so any row it may mean counts unless the caller knows the hash.
the signature algorithm's object identifier
Optionalhash: string
the node digest name, where the parameters gave one
the cause, or null where it may
StaticacceptWhy the ambient realm may not accept an XML DigestMethod.
the digest's label, as SHA-256
the cause, or null where it may
StaticdefaultThe algorithm a JOSE signature uses where nothing names one: the first
usable element of a configured list, else RS256, else, under
keys.pqcOnly, the first post-quantum one. A specification's own default
is its caller's to apply first.
the JOSE name
StaticdescribeEvery surface's rows and each row's state, in preference order: what the
console draws and /crypto/metadata publishes.
surface to { signList, acceptList, rows }
Staticeddsawhether the ambient realm signs with EdDSA and publishes its OKP
signing keys (keys.eddsaSigning, off by default)
StaticeffectiveThe algorithms the ambient realm may use on a surface. An empty setting means today's order, not preference order: post-quantum signing is on by default, so preference order would move every default signature to ML-DSA.
the surface
sign or accept
the surface's names, in order
Staticjosekeys.signingAlgorithms as a list, RS256 always in it, in the order
configured. OpenID Connect Discovery requires RS256.
the list, or null where it is empty: every algorithm the realm otherwise has
StaticnarrowNarrows, in place and at any depth, the lists that say what this realm
ACCEPTS to the accept lists. A number in a list is a COSE identifier
(OpenID4VP's mso_mdoc). Members in except, which list what it signs,
are the caller's.
the metadata document
member names to leave alone
the same document
StaticnarrowNarrows, in place, the top-level members that say what this realm SIGNS,
into a configured list's order. id_token_signing_alg_values_supported
keeps RS256 under keys.pqcOnly, which OpenID Connect Discovery requires.
the metadata document
the names of the members that list what it signs
the same document
Staticomitswhether ES256K is left out for want of a list: product mode
(mode.omitsUnapprovedSigningCurves()) and no keys.signingAlgorithms
Staticpostwhether the ambient realm signs, publishes and verifies the
post-quantum JOSE algorithms (keys.postQuantumSigning, on by default)
Staticpqcwhether the ambient realm signs only post-quantum
StaticpublishedWhether a JWK Set still publishes a signing key under keys.pqcOnly: the
post-quantum ones, and the RSA key RS256 ID Tokens verify with.
the key
true when it stays
Staticrefusesthe surface
the row id
the surface's accept list, parsed
whether a signature in that row is refused for its curve
StaticsignWhy the ambient realm may not sign with an algorithm.
the surface
the surface's name for it, or its row id
Optionalcontext: SignContext
idToken, for RS256's place under keys.pqcOnly
the cause, or null where it may. none and a name no row has are
null: not a signature here, or the engine's own refusal to make
Staticunapproveda JOSE algorithm name
whether that algorithm is on an unapproved curve the ambient
realm leaves out (omitsUnapprovedCurves())
StaticunderThe algorithm a setting's choice signs with under keys.pqcOnly: its own,
unless that flag is what refuses it. Narrower than usableSigningAlg(),
for a setting whose other refusals are documented as the operator's to
avoid (oid4vci.credentialSigningAlgorithm).
the algorithm a setting names
the algorithm to sign with
StaticwriteThe rule the lists hold at every write. A list names nothing twice; a
realm accepts what it signs, so it cannot refuse its own tokens; a setting
choosing one algorithm chooses within its list; and keys.pqcOnly needs
post-quantum signing on.
the setting being written
its value, parsed
OptionalinRealm: boolean
whether the write lands in a realm's overrides
Optionalbeside: (other: string) => unknown
a companion setting's value as this write leaves it
{ problem, code }, or null
StaticxmlWhat the SAML V2.0 Metadata Profile for Algorithm Support publishes. Its section 2.4 is "an entity's capability to VERIFY digests and signatures", each kind "listed in order of preference", so this is the accept list and NOT what this realm signs with: a peer picks the first it supports to send here. Preference order, strongest first. Never a weak method, and never an HMAC, which is a Kerberos session key's and no certificate's.
every digest method's URI to its row
{ signing, digests }, URIs
StaticxmlThe row saml.signatureAlgorithm's short name means: the fragment of its
URI, which is how every one of them is spelled.
the short name, as rsa-sha256
the row, or null
Why the ambient realm may not accept a signature in an algorithm. Asked before any key operation.