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 administer unique client IDs for every customer
- Scalability: Customers can be added without requiring considerable infrastructure changes
Resources
Accessing the Test environment's predefined synthetic entity
In Production, a main entity would normally delegate access to a vendor through Altinn. Delegating such access makes it possible for the vendor to operate on behalf of the main entity when acquiring HelseID access tokens.
Note
Delegating access through Altinn is not supported in HelseID's Test environment. In Test, a vendor might delegate access for itself on behalf of a synthetic entity.
For the JFT service, the synthetic entity with organization number 313231593 has been populated with test data. One of the following two methods might be used to get access to this entity:
- Create a single-tenant client configuration and specify org.number
313231593. - Create a multi-tenant client configuration and add delegation of access for
313231593.
Note
As 313231593 has been created by NHN it cannot be used to simulate service offers.
Creating client configurations
HelseID Self-service Test can be used for creating new client configurations. In order to access JFT-API please specify the API nhn:jft and its scope nhn:jft/api.
Note
The Test environment only accepts synthetic entities. Do not use real-world org.numbers in Test.