Skip to content

Fortified IDDocs

CSC signing

Configure the customer CSC API subset with real SAML identity, OAuth code authorization, separate consent and exact digest binding.

The CSC service lets a registered application obtain signatures over approved digests with configured credentials. Signing Server provides the supported CSC API 2.2.0.0 subset and an OAuth authorization server; the external identity provider authenticates the person with SAML. The configuration selector is service: "csc-v1", while the wire endpoints are under /csc/v2.

Start from the CSC configuration example and configuration schema. Replace every placeholder with your own protected files, registered identities and certificate pins.

  • Register each client's client_id, kid, RSA public-key file, display name, exact HTTPS redirect URIs and permitted connections. The client keeps its private requester key.
  • Configure the SAML connection, subject attribute and required authentication context. CSC uses its own SP/audience, ACS path and browser namespace.
  • Map each public credential_id to its enabled signing credential, verified owner, connection, permitted client IDs and actual leaf-certificate SHA-256.
  • Keep requester, TLS, SAML signing/decryption and document keys distinct. A request cannot choose a private-key alias, module, file or PIN.
  • Use distinct migration/runtime database accounts, including on PostgreSQL. Prepare the canonical signing and dedicated OAuth schemas from the exact same packaged runtime that will start the service.

The owner is saml- followed by SHA-256 hex of idpEntityId + NUL + subjectAttribute + NUL + canonicalSubject. This administrator mapping does not authenticate a person. The supported directory selects supplied static PKCS#12 or pinned PKCS#11 credentials; dynamic and provisioned enrollment selectors are outside this CSC profile.

Method and path Purpose
POST /csc/v2/info Discover the supported subset and OAuth base.
POST /csc/v2/credentials/list Discover accessible credentials for the authenticated client and verified signer.
POST /csc/v2/credentials/info Read permitted public credential information.
POST /csc/v2/signatures/signHash Sign the complete approved digest batch once.
POST /csc/v2/oauth2/pushed_authorize Submit an authenticated, immutable pushed authorization request (PAR).
GET /csc/v2/oauth2/authorize Start the browser flow for this server's owned PAR URI.
POST /csc/v2/oauth2/token Redeem one authorization code with client authentication and the S256 verifier.
POST /csc/v2/oauth2/revoke Revoke the authenticated client's own token.
POST /csc/saml/acs/{connection} Accept the fresh signed/encrypted identity response.
POST /csc/consent/{flow} Receive the separate browser approval or cancellation with its private cookie and CSRF value.

info.oauth2 is the configured service origin plus /csc/v2. Append oauth2/authorize, oauth2/pushed_authorize, oauth2/token or oauth2/revoke once. Unsupported operations are not advertised and return 404; wrong methods on supported routes return 405.

  1. The client submits PAR with response_type=code, the exact registered redirect, scope, state, connection and mandatory S256 PKCE challenge. A credential request also binds credentialID, SHA-256 algorithm, numSignatures and all digest occurrences.
  2. The browser opens the authorization endpoint with that client's owned request_uri. An arbitrary external URI is never fetched.
  3. The configured IdP returns a fresh signed/encrypted SAML response. Signing Server checks the private browser correlation, issuer, audience, recipient, assurance, time and subject.
  4. Signing Server displays the registered client and either discovery-only approval or the exact credential, algorithm, count, digests and client-supplied description. The person explicitly approves or cancels.
  5. The server redirects to the registered URI with the original state, service-origin iss, and a code or denial. The client verifies state and issuer.
  6. The client redeems the code once, with a fresh client assertion, exact redirect and original PKCE verifier.

PAR, token and revocation use private_key_jwt: RS256 with the registered client key, iss=sub=client_id, fresh jti, integer iat/exp with at most 60 seconds lifetime and aud equal to the exact receiving endpoint. Assertions are durably one-use. Use a fresh assertion for each new request; a failed request does not authorize signing retry.

A service token permits scoped discovery and information. It cannot sign. A credential authorization requires verified identity matching the owner and explicit approval of the exact batch. It can be requested directly for a known credential. If a service token is supplied as its parent, that same client and signer remain bound and parent revocation/expiry blocks later consumption.

The signing subset is RSA PKCS#1 v1.5 with SHA-256, one complete batch of 1–64 raw 32-byte digests. PAR hashes is CSV base64url; signHash hashes uses canonical padded standard Base64. Preserve duplicate occurrences and their counts. The server matches the whole authorized multiset, permits reordered hashes, signs once and returns results in the requested order. A subset, extra digest or changed count is rejected.

Use either the credential token as Bearer without SAD, or the matching service Bearer with the credential token in SAD. Conflicting tokens are rejected. No refresh, password/implicit grant, dynamic client registration, PIN authorization, credential issuance, asynchronous signing or document upload is advertised by this profile.

Default ceilings are PAR 120 seconds, browser ceremony 180 seconds, code 30 seconds, service token 300 seconds and signing token 30 seconds. Every authority is additionally bounded by its original request, identity, consent and certificate validity. A callback or successful login alone grants no signing authority.

Replay, mismatch, revocation and expiry fail closed. Canonical consumption and current grant checks precede private signing. An uncertain outcome remains consumed: do not retry or reset it. Pending browser state is lost on restart; durable replay, consumption and revocation state remain.

The downloadable reference describes client registration, authorization, digest signing and database operation for version 1.0.0.

The supported CSC installation profiles are listed in Supported platforms and scope.