IduraDocumentation
  1. Verify
  2. Getting Started
  3. Set up the Dashboard

Before you integrate Idura Verify into your application, you need to configure your environment in the Idura Dashboard. It takes about two minutes and gives you the client credentials required to build your own eID-based login flows.

Create a tenant

A tenant represents your organization’s isolated environment at Idura.

  1. Sign up for a free test account to access the Idura Dashboard.
  2. You will be prompted to create your first tenant. You can change the tenant name at any time after creation in the Dashboard Settings.

Risk-free testing: Your free account includes a sandbox environment with unlimited test logins, so you can build and test your integration without any obligations or unexpected costs.

Register a domain

Everything you do with Idura requires a domain to route your authentication requests.

  1. From the Domains tab of your Dashboard, register a new domain.
  2. Select your domain type. We recommend starting with a standard .test.idura.broker domain for your local development and testing.
  3. Type your domain name in the Domain settings field. If your company name is Acme Corp, your first domain may look something like acme-corp.test.idura.broker.

Create a Verify application

An application represents the software you are building (e.g., your React frontend or Node.js backend). Creating an application generates the client credentials your code needs to communicate with Idura Verify.

  1. From the Applications tab of your Dashboard, create a new Verify application.
  2. Configure your application:
  • Name: Choose a recognizable name.
  • Domain: Select the domain you registered in the previous step.
  • Client ID / Realm: You can use the auto-generated identifier (e.g., urn:my:application:identifier:123) or create a custom one.
  • Redirect URL(s): Enter the callback URL where Idura should send users after they log in (e.g., http://localhost:3000/api/auth/callback for local development). Note: Wildcards are not supported, but you can always add more URLs to the list.
  • Application Type: Select the option that matches your tech stack (e.g., Single Page Application -> React, Regular Web Application -> Node.js). If your selection requires a client secret, Idura will automatically generate one for you in the next step.
  1. Click Create application to save the initial configuration.
  • If you’re presented with a client secret, copy and save it in a secure location. Note that if you navigate away from this page without copying and saving the client secret, you will have to generate a new one. OAuth2 client secret
  • Your application settings will now display the Client ID / Realm. You will need to paste it in your code once ready to integrate.

Lost your client secret?

Client secrets are for server-side applications only. If you are building a Single-page application or a native mobile app, you cannot securely store a secret. Use PKCE instead.

If you lost your client secret or need to generate one, you can do so from your Application settings.

  1. Go to the OpenID Connect section of your Application settings.
  2. Toggle on Enable OAuth2 Code Flow and click Save. Enable OAuth2 Code Flow toggle
  3. Copy and save the generated client secret. Idura only stores the secret as a hashed value, meaning that once you navigate away from this page, you won’t be able to retrieve the raw value again. If you lose your client secret, you will have to generate a new one and update your code. OAuth2 client secret

For maximum security in production, we recommend moving away from client secret authentication and replacing it with safer alternatives:

Learn more in our OpenID Connect security best practices guide.

What’s next?

Your Dashboard is configured and your client credentials are ready to use.

To run test logins, you need a test user for each eID you plan to use. Note that you can’t use your real, personal eID in a Test environment.

Ready to test? Create your first test user.