Integration with Signicat e-ID Hub
About the provider
Signicat’s main focus is on digital verification, authentication and signing (also conforming with EUDI wallet regulations). The Signicat e-ID Hub allow customers to verify the identity of users who log in to online services. The e-ID Hub gives access to a hub of European e-IDs through a single point of integration with the following authentication protocols:
- OpenID Connect (OIDC)
- Security Assertion Markup Language (SAML) 2.0
- Signicat Authentication REST API
You can find the list of current e-ID integrations in the Signicat documentation.
Required changes to make it work in your environment
Signicat side
- You have to create a BankID demo client and a test user by following the linked documentation pages.
- On the the Signicat dashboard page create and note the Signicat Client ID and secret:
- Also note the value of the “Well-known URL for client”:
Nevis side
- Under Resources > Secret & Files, create two Kubernetes secrets (scoped to the relevant environment) for the Signicat client ID and client secret values. To learn more about using secrets in Nevis ID, visit the Manage Secrets page.
- Under Configuration > Variables, refer to the created secrets by specifying their paths in the
signicat-client-idandsignicat-client-secretvariables. Secrets already populated in these properties are for demonstration only and can be changed to fit your deployment.
- Store the value of the “Well-known URL for client” from the Signicat OIDC client configuration into the “signicat-provider-endpoint” variable and finally deploy the project:
