Initial preparations

Before you can start integrating with Signicat's implementation of ID-porten in production, be aware of the following prerequisites.

Access to ID-porten

Before you can create a production account, you need to configure ID-Porten access with an onboarding manager. To get help with this, please contact us.

Initial setup in Dashboard

Once you have received the needed access to the ID-porten service, you can add a production account, connect a domain to the account and add ID-porten to the Dashboard.

Create a production account

To create the production account from the Signicat Dashboard:

1. Go to Signicat Dashboard > Organisation management.
2. Click Add Account.
3. Enter the name of your account under Account Name.
4. Tick the Production account type.
5. Click Create to create the new account.

Set up domain

When you have created a production account, you can add a domain to this account.

1. In the Signicat Dashboard, navigate to Settings > Domain management. If you are a member of multiple accounts, make sure you are in the correct account by checking the account name in the top left of the screen.
2. Select Add domain.
3. To add a standard (Signicat) domain, enter the name of your subdomain in the Domain name field.
4. Select Add domain to create the new domain.

For more setup options, see domains in the Dashboard setup section.

Add ID-porten to the Dashboard

1. In the Signicat Dashboard, navigate to Products > eID and Wallet Hub > eIDs.
2. Select + Add new in the top right.
3. Choose the eID from the list. Add any required configuration, then select Add.
4. Now, review that the eID is available and set to "Active" in the eIDs list.

Select a protocol

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

Supported authentication protocols

Signicat supports the standard OpenID Connect (OIDC) and SAML 2.0 protocols. In addition, we offer our bespoke Signicat Authentication REST API.

The protocol you choose depends your goals and preferences. The Authentication REST API provides flexibility and an easy setup. Otherwise, we recommend OIDC, since SAML 2.0 is much more complex to implement and usually requires a federation agent. OIDC is an industry standard with managed user sessions, unlike the Authentication REST API.

To learn more about these authentication protocols, see the Signicat eID and Wallet Hub documentation.

Next steps

Continue the integration with your chosen authentication protocol:

Integration with OIDC

Integrate with ID-porten using OpenID Connect

Integration with REST API

Integrate with ID-porten using Signicat Authentication REST API

Integration with SAML 2.0

See the general eID and Wallet Hub documentation