Skip to main content
Developer

JWKS#

View as Markdown
On this page

Overview#

The /jwks endpoint provides the public key for validating SignerInfo JWTs returned with signing results.

SignerInfo JWT Claims#

When you request SignerInfo JWT in your sign order (resultContent.requestSignerInfo: true), the response includes a signed JWT containing information about the document signer extracted from their digital certificate.

ClaimDescriptionExample
subCertificate serial number"UN:NO-9578-5100-Q_5iVtjvP..."
issIssuer (the SignDoc service domain)"api.esign-stoe.cloud"
nameFull name of the signer"Ola Nordmann"
given_nameFirst name"Ola"
family_nameLast name"Nordmann"
birthdateDate of birth (YYYY-MM-DD format)"1988-09-05"
signature_qualitySignature quality level"QES" or "AES"
cert_issuerCertificate issuer DNCertificate authority information
iatIssued at timestampUnix timestamp
expExpiration timestampUnix timestamp
nbfNot before timestampUnix timestamp
2.16.578.1.61.2.3BankID PID"UN:NO-9578-6000-4-1911943"
2.16.578.1.61.2.4Norwegian National Identity Number (if present)"09058812345"
2.16.578.1.61.2.1eID country code"NO"
2.16.578.1.61.2.2eID scheme"BANKID"

Validation Guidelines#

  1. 1

    Retrieve the public key from this endpoint

  2. 2

    Verify the JWT signature using the public key

  3. 3

    Validate that the token hasn't expired (exp claim)

  4. 4

    Verify the issuer (iss claim) matches the expected SignDoc domain

  5. 5

    Extract and trust the signer information claims

API Specification#

Was this page helpful?