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
| Artifact | Purpose |
|---|---|
| TrustedX-CSCv2.postman_collection.json | Executable CSC API integration example with basic validations and tests |
| TrustedX-CSCv2.postman_environment.json | Environment 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:
- Import the Postman collection and environment configuration.
- Populate the environment variables with the values assigned to your client.
- Execute the CSC info request and verify successful connectivity to the CSC service.
- In the 10 - Obtain Signing Data Using a PAR Authorization Request folder, execute all requests sequentially.
- In the 20 - Hash Signing folder, execute all requests sequentially.
-
Using Postman Console, compare the actual HTTP requests and responses with the parameters and examples provided in this documentation.
Automatic Storage of Postman VariablesThe post-response scripts of token requests automatically store the
access_tokenand, during the signing credential acquisition flow, also thecredential_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
credentialIDand 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_uriparameter must exactly match the OAuth client configuration, PAR request, authorization request, and token exchange request.
Environment Endpoints
Postman Environment Variables
Required Configuration Parameters
| Variable | Required | Description |
|---|---|---|
csc_base_url | Required | CSC v2 base URL without a trailing slash |
client_id | Required | Registered OAuth client identifier |
client_secret | Required | OAuth client secret |
redirect_uri | Required | Redirect URI registered for the OAuth client |
scope | Required | OAuth scope. In this scenario, use the value credential |
Credential Acquisition Parameters
| Variable | Required For | Description | Example |
|---|---|---|---|
signature_qualifier | Credential acquisition | Requested signature qualification level | eu_eidas_qes |
acr_values | Authorization | Defines the authentication flow to be used | See below |
Supported Authentication Flows
| Authentication Method | Value |
|---|---|
| eID Card | urn:eparaksts:authentication:flow:sc_plugin |
| eID Scan | urn:eparaksts:authentication:flow:mobile-eid |
Signing Parameters
| Variable | Required For | Description |
|---|---|---|
credential_id | Signing | eIDAS-assigned signing credential identifier |
hash_base64 | Signing | Previously calculated document hash in Base64 format |
hash_algorithm_oid | Signing | OID of the hash algorithm used |
signature_algorithm_oid | Signing | OID of the requested signature algorithm |
Supported Algorithms
| Algorithm | OID |
|---|---|
| SHA-384 | 2.16.840.1.101.3.4.2.2 |
| ECDSA with SHA-384 | 1.2.840.10045.4.3.3 |
Dynamic Parameters
These parameters are populated automatically by the Postman collection during execution.
| Variable | Description |
|---|---|
code_verifier | Cryptographically random PKCE verifier |
code_challenge | SHA-256 value of code_verifier, encoded in Base64URL format |
oauth_state | OAuth correlation and CSRF protection value |
request_uri | Request reference received from the PAR response |
authorize_url | Generated authorization URL used for user redirection |
authorization_code | Single-use authorization code received through the callback redirect |
access_token | Bearer Access Token received from the Token endpoint response |
Next Steps
After completing the environment configuration:
- Execute the
POST /inforequest to verify connectivity with the CSC service. - Create a short-term signing credential.
- Perform user authentication.
- Retrieve credential information.
- Authorize signing of the document hash.
- Call
POST /signatures/signHashto obtain a Qualified Electronic Signature (QES).
Updated 18 days ago