HelseID
Client configuration: Single-tenant vs. multi-tenant
As a rule of thumb:
- Multi-tenancy is recommended for cloud-based services (SaaS).
- Single-tenancy is recommended for locally installed applications.
Note
What is a multi-tenant client? A multi-tenant client can represent multiple main entities in HelseID.
Why use multi-tenancy?
- Maintainability: No need to manage a unique client ID for every customer.
- Scalability: New customers can be onboarded without significant infrastructure changes.
Resources
Accessing the Test environment's predefined synthetic entity
In Production, a main entity typically delegates access to a vendor through Altinn. This delegation allows the vendor to acquire HelseID access tokens on behalf of the main entity.
Note
Delegating access through Altinn is not supported in HelseID's Test environment. In Test, a vendor must delegate access for itself on behalf of a synthetic entity.
For the JFT service, the synthetic entity with organization number 313231593 has been pre-populated with test
data. Use one of the following methods to gain access to this entity:
- Create a single-tenant client configuration and specify org. number
313231593. - Create a multi-tenant client configuration and add a delegation for
313231593.
Note
Since 313231593 was created by NHN, it cannot be used to simulate service offers.
Creating client configurations
Use HelseID Self-service Test to create new client configurations.
To access the JFT API, specify the API nhn:jft and its scope nhn:jft/api.
Note
The Test environment only accepts synthetic entities. Do not use real-world organization numbers in Test.