Quickstart

To simplify the integration of the Remote eID Signature solution (based on the CSC API), we provide a ready-to-use Postman collection and an environment configuration template.

Available Downloads

 

ArtifactPurpose
TrustedX-CSCv2.postman_collection.jsonExecutable CSC API integration example with basic validations and tests
TrustedX-CSCv2.postman_environment.jsonEnvironment configuration template without customer-specific data and secrets
 

Recommended Execution Sequence

To successfully complete the full Remote eID Signature workflow, it is recommended to perform the steps in the following order:

  1. Import the Postman collection and environment configuration.
  2. Populate the environment variables with the values assigned to your client.
  3. Execute the CSC info request and verify successful connectivity to the CSC service.
  4. In the 10 - Obtain Signing Data Using a PAR Authorization Request folder, execute all requests sequentially.
  5. In the 20 - Hash Signing folder, execute all requests sequentially.
  6. Using Postman Console, compare the actual HTTP requests and responses with the parameters and examples provided in this documentation.

    🚧

    Automatic Storage of Postman Variables

    The post-response scripts of token requests automatically store the access_token and, during the signing credential acquisition flow, also the credential_id. Ensure that the correct Postman environment is selected and that scripts have permission to update local environment values.

Scope

 
The Postman collection covers the following operations:

  • CSC service information retrieval (POST /info);
  • short-term signing credential registration;
  • OAuth Authorization Code acquisition using PAR (Pushed Authorization Request) and PKCE;
  • exchange of the authorization code for a Bearer Access Token;
  • retrieval of credentialID and credential information;
  • authorization of document hash signing;
  • hash signing using POST /signatures/signHash.
     

Prerequisites

Before starting the integration, the following must be obtained:

  • OAuth client_id;
  • OAuth client_secret;
  • registered redirect_uri;
  • access to the appropriate environment (test or production);
  • a test user for authentication and signing validation.
     

Important! The value of the redirect_uri parameter must exactly match the OAuth client configuration, PAR request, authorization request, and token exchange request.

Environment Endpoints

Postman Environment Variables

Required Configuration Parameters

VariableRequiredDescription
csc_base_urlRequiredCSC v2 base URL without a trailing slash
client_idRequiredRegistered OAuth client identifier
client_secretRequiredOAuth client secret
redirect_uriRequiredRedirect URI registered for the OAuth client
scopeRequiredOAuth scope. In this scenario, use the value credential

Credential Acquisition Parameters

VariableRequired ForDescriptionExample
signature_qualifierCredential acquisitionRequested signature qualification leveleu_eidas_qes
acr_valuesAuthorizationDefines the authentication flow to be usedSee below

Supported Authentication Flows

Authentication MethodValue
eID Cardurn:eparaksts:authentication:flow:sc_plugin
eID Scanurn:eparaksts:authentication:flow:mobile-eid

Signing Parameters

VariableRequired ForDescription
credential_idSigningeIDAS-assigned signing credential identifier
hash_base64SigningPreviously calculated document hash in Base64 format
hash_algorithm_oidSigningOID of the hash algorithm used
signature_algorithm_oidSigningOID of the requested signature algorithm

Supported Algorithms

AlgorithmOID
SHA-3842.16.840.1.101.3.4.2.2
ECDSA with SHA-3841.2.840.10045.4.3.3

Dynamic Parameters

These parameters are populated automatically by the Postman collection during execution.

VariableDescription
code_verifierCryptographically random PKCE verifier
code_challengeSHA-256 value of code_verifier, encoded in Base64URL format
oauth_stateOAuth correlation and CSRF protection value
request_uriRequest reference received from the PAR response
authorize_urlGenerated authorization URL used for user redirection
authorization_codeSingle-use authorization code received through the callback redirect
access_tokenBearer Access Token received from the Token endpoint response

Next Steps

 After completing the environment configuration:

  1. Execute the POST /info request to verify connectivity with the CSC service.
  2. Create a short-term signing credential.
  3. Perform user authentication.
  4. Retrieve credential information.
  5. Authorize signing of the document hash.
  6. Call POST /signatures/signHash to obtain a Qualified Electronic Signature (QES).

Did this page help you?