Get started with the integration

Have you tried it out in sandbox?

We recommend that you test our services with your sandbox account before implementing them in production.

Prerequisites

Access to SmartID

Before you can create a production account, you need to configure Smart-ID access with an onboarding manager. To get help with this, please contact us (opens new window).

Define the service provider name

When enabling access, your onboarding manager will ask you what service provider name you prefer to be displayed for your end-users in the login screens. Signicat will send this to SK ID solutions and let you know when this name is approved. This name will be the same for both Smart-ID and Mobiil-ID.

Certificate information

There are no certificate exchanges needed to use Smart-ID.

Create a production account in the Dashboard

Once you have received the needed permissions, you can create the account from the Signicat Dashboard:

1. Log into the Dashboard (opens new window).
2. Click the name of your organisation at the top left of the screen and then select Manage.
3. Under Organisation management, click Add Account.
4. Enter the name of your account under Account Name.
5. Tick the Production account type.
6. Click Create to create the new account.

Add ID method to the Dashboard

1. In the Dashboard, navigate to eID Hub > ID Methods (opens new window).
2. To enable the ID method, click Add new in the top right.
3. Choose the ID method from the list. Then, click Save.
4. Now you can see the ID method listed and enabled with status "Active" in the ID methods list.

Select protocol

To establish a connection between Signicat Smart-ID and your application, you need to use a standard authentication protocol.

Supported protocols

Signicat supports the standard OIDC and SAML 2.0 protocols. In addition, we offer the Signicat Authentication REST API.

Choice of protocol depends on what you prefer and what you want to achieve. The Authentication REST API gives you a lot of flexibility and is easy to set up. Between the other two, we recommend using OIDC, since SAML 2.0 is much more complex to implement on your side and usually requires a federation agent already in place. OIDC is industry standard and you do not need to manage user sessions on your own (like with the Authentication REST API).

For more information about the different protocol types, see the general Authentication protocols section.

Set up the protocol

For information about how to set up the different protocols, see the Quick start guide.