-
Notifications
You must be signed in to change notification settings - Fork 4
Update Verify's "Getting Started" section #308
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
nmoskaleva
wants to merge
4
commits into
master
Choose a base branch
from
update-intro-sections
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
48f753d
Move tech and eID logos to `components` folder
nmoskaleva 4e7dcae
Update Verify's "Getting Started" section to improve developer experi…
nmoskaleva 2349b8c
fixup! Update Verify's "Getting Started" section to improve developer…
nmoskaleva b21dc38
fixup! fixup! Update Verify's "Getting Started" section to improve de…
nmoskaleva File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
File renamed without changes
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,65 @@ | ||
| --- | ||
| product: verify | ||
| category: Getting Started | ||
| sort: 1 | ||
| title: Set up the Dashboard | ||
| subtitle: Create a tenant, register an application, and generate client credentials. | ||
| --- | ||
|
|
||
| Before you can integrate Idura Verify into your application, you need to configure your environment in the Idura Dashboard. | ||
| This takes about two minutes and will give you the client credentials required to build your own eID-based login flows. | ||
|
|
||
| ## Create a tenant | ||
|
|
||
| A [tenant](/verify/how-it-works/core-concepts/#tenants) represents your organization's isolated environment at Idura. | ||
|
|
||
| 1. [Sign up for a free test account](https://dashboard.idura.app/signup) to access the Idura Dashboard. | ||
| 2. You will be prompted to create your first tenant. | ||
|
|
||
| <Highlight> | ||
| **Risk-free testing**: Your free account includes a sandbox environment with unlimited test | ||
| logins, allowing you to build and test your integration without any obligations or unexpected | ||
| costs. | ||
| </Highlight> | ||
|
|
||
| ## Register a domain | ||
|
|
||
| Everything you do with Idura requires a [domain](/verify/how-it-works/core-concepts/#domains) to route your authentication requests. | ||
|
|
||
| 1. Go to the [**Domains** tab](https://dashboard.idura.app/domains) in your dashboard. | ||
| 2. Click **Register domain**. | ||
| 3. Select your domain type. We recommend starting with a standard `.test.idura.broker` domain for your local development and testing. | ||
| 4. Type your domain name in the **Domain settings** field. If your company name is Acme Corp, your first domain may look somethig like `acme-corp.test.idura.broker`. | ||
|
|
||
| ## Register an application | ||
|
|
||
| An [application](/verify/how-it-works/core-concepts/#applications) represents the software you are building (e.g., your React frontend or Node.js backend). | ||
| Registering an application generates the client credentials you will use in your code to configure your software to communicate with Idura Verify. | ||
|
|
||
| 1. Add a [new login application](https://dashboard.idura.app/applications/add/) from the **Applications** tab of your dashboard. | ||
| 2. Configure your new 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](/verify/reference/glossary/#redirect-uri) 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). This will point you to the right integration guide once the application is created. | ||
|
|
||
| 3. Click **Create Application** to save the initial configurations. | ||
| Your application settings will now display the **Client ID / Realm**. You will need to paste it in your code once ready to integrate. | ||
|
|
||
| ### Generate a client secret | ||
|
|
||
| import GenerateClientSecretSnippet from '../../../snippets/generate-client-secret.mdx'; | ||
|
|
||
| <GenerateClientSecretSnippet /> | ||
|
|
||
| ## What's next? | ||
|
|
||
| Your dashboard is configured and your API credentials are ready to use. | ||
|
|
||
| To be able to run test logins, you need to create a test user for the eID(s) you're planning to use. | ||
| Note that you can't use your real, personal eID in a test environment. | ||
|
|
||
| [Create test users →](/verify/getting-started/test-users/) |
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
fromPathdoes not appear to exist today? https://docs.idura.app/verify/articles/custom-ui-css