Other

Signicat provides a service called “demo”. This is intended for demo and testing purposes while you await your own customer-specific service. Once you have signed a contract with Signicat, you and your company will get your own service that you should use for all testing purposes.

Details for Signicat’s demo service are as follows:

Servicename: demo

WS Password: Bond007

Test users: See separate pages for each ID method.

This page lists details on methods for authentication and signing that are available in Signicat’s demo service. For more help and guidelines, please visit Get started with authentication or Get started with signatures to learn more about how services are utilized.

• OIDC considerations
• Authentication methods
• Authentication-based signing methods
• Third-party signing methods
• Assure
• Portals
• Graphical profiles
• Packaging method
• Supported URL parameters

OIDC considerations

We have set up a ‘demo-preprod’ client to be used when OpenID Connect is utilized as the authentication protocol. For this client, the scope “profile” is available for all ID methods. Other scopes may be available depending on the ID method used.

When calling the OIDC endpoint, you will need to submit the client secret for the “demo-preprod” client. Here are the details for Signicat’s two preproduction environments (Nordics and Europe):

The OIDC server will redirect the user to a redirect URI once the user has finished authenticating and authorizing the access for your client. The following redirect URIs are preconfigured and may be used:

• https://localhost:8080/redirect
• https://localhost:5000/redirect
• https://localhost/redirect
• http://localhost/redirect

You may contact support@signicat.com to set up an additional redirect URI for use.

List of scope and claims available if supported by the ID method in question

Authentication methods

See also:

• SAML response examples
• Supported URL parameters (this page)
• ID methods for high-level information

Authentication-based signing methods

Refer to our Signing documentation for more information on authentication-based signing.

*PAdES (PDF Advanced Electronic Signatures) requires Packaging service (packaging method “pades” and “ltvsdo-validator” as validation method). PAdES does not support text.

**LTV-SDO means Long Term Validation SDO. This is a signed data object (SDO).

See also ID methods for high-level information.

Third-party signing methods

Refer to our Signing documentation for more information on third-party signing.

*PAdES (PDF Advanced Electronic Signatures) requires Packaging service (packaging method “pades” and “ltvsdo-validator” as validation method). PAdES does not support text.

**LTV-SDO means Long Term Validation SDO. This is a signed data object (SDO).

See also ID methods for high-level information.

Assure

Note: Since this is a non-production environment, you should not use real ID documents when testing. Be aware that this service is shared with anyone, so other people can look into any dossier or process using these credentials.

Credentials:

Client ID: assure-api-test-client
Secret: jfKBjVz-hclajTP9sBlO2sg4XZO1lwiQzxu6WcGUxr8
Endpoint: https://preprod.signicat.com/

See also Identity verification with Signicat Assure for high-level information.

Sign API

Note: Please find documentation on how to use the Sign API here.

Credentials:

Client ID: demo-preprod
Secret: mqZ-_75-f2wNsiQTONb7On4aAZ7zc218mrRVk1oufa8
Scope: client.signature
Endpoint: https://preprod.signicat.com/

Portals

Authentication portals might be used when the user has to choose between two or more methods.

Graphical profiles

Packaging method