This tutorial demonstrates how to integrate Criipto Verify with Auth0. Following steps are required to complete your first login:
In the following you will be configuring first Criipto Verify, then Auth0, and finally finishing the Criipto Verify configuration with the information you get from Auth0. Once configured you may test that everything works from Auth0.
First, you must register your Auth0 tenant as an application in Criipto Verify.
Once you register your Auth0 tenant, you will also need some of the information for configuring Auth0 to communicate with Criipto Verify. You get these details from the settings of the application in the dashboard.
Specifically you need the following information to integrate with Auth0:
If you are registering a new application, you must first save the configuration.
Once you have a saved application registration you may configure the OAuth2 code flow.
Open the application registration and configure it for the right OAuth2 flow:
plainJsonto enable retrieval of plain JSON user information from the
Note that this is the only time you will be shown the actual value of the client secret. Criipto only stores this as a hashed value, which means you cannot retrieve the value once it has been generated and stored.
Some libraries do not support the final
userinfo request. In those cases you will need to fetch the user data directly from the
token endpoint as opposed to the
userinfo endpoint. Do this by choosing the appropriate option as shown below.
You may configure Criipto Verify to retrieve the user information from either the
userinfo endpoint - the default option - or you may explicitly choose the
fromTokenEndpoint in the user info response strategy instead:
To integrate Criipto Verify with Auth0, you create an Auth0 OpenID Connect connection to communicate with Criipto Verify. Because Auth0 will not pass the
acr_values to Criipto Verify, you will have to create a new connection for every e-ID option that you intend to use. (
acr_values is a parameter in the
/authorize request to Criipto Verify needed to specify which kind of e-ID is requested)
For those cases, you can leverage our login-method specific metadata endpoints. Each of these contain an embedded and base64-encoded variant of the "raw" value normally supplied in the
For example, the
acr_values of Norwegian BankID login method is
urn:grn:authn:no:bankid. This translates to
dXJuOmdybjphdXRobjpubzpiYW5raWQ= in base64 (UTF-8 charset), so the metadata endpoint will be:
Below is a list of supported login methods with corresponding base64 encoded
acr_values. Choose the once you intend to use.
|Login method||acr_values||base64 encoded|
|Mobile or Web (user choice):|
|Norwegian Vipps Login|
|Login with Vipps app:|
|All options (user chooses):|
|Another device (aka mobile):|
|Personal with code card:|
|Employee with code card:|
|Employee with code file:|
|Mobile certificate (Mobiilivarmenne):|
|Both of the above:|
|Sofort (with Schufa check):|
You create an OIDC connection for every login method you intend to use.
After you save a connection, you may get an error: "Error! Something happened while trying to save your connection: Issuer metadata missing the following attributes: token_endpoint".
This is due to a bug in Auth0's frontend, nothing to worry about. In this case, under the Issuer URL select Show Issuer Details and under Token Endpoint enter
If you are creating multiple connections, you have to enter Callback URL only once. It will be the same for every OpenID Connect connection.
To test your OpenID Connect connection, go back to the list of all OpenID Connect connections and select Try button on the right side of the connection you want to test.
Almost all e-ID types have a notion of test users and real users.
Real users are real people logging in to a web site, thus voluntering their real name and typically also a social security number, SSN.
Test users are either created by you for the occasion, or we provide you with access to already created test users.
You may ready more in the section on e-IDs
How to integrate your application with Auth0 depends on the technology you are working with. Refer to the Auth0 quickstart guide for more details.