Account Component
The account component adds a number of data elemets to manage user interaction such as login and data access:
Account, User, UserGroup ,Profile and DataAccess.
A user belongs to an account (i.e. an organization) and has a certain profile (e.g. user, administrator, super user). A user can also belong to a certain user group.
Data access can be configured at 3 levels: for a usergroup, for a profile and for an individual user.
Access to the following elements can be configured:
- Data elementsData Element (DataElement). A fundamental data concept or entity within an application's domain, acting as an anthropomorphic translation of a real-life object or concept.
- Data operationsData Operation (DataOperation). A type-safe action (e.g., Create, Update, Custom) executed on DataElement instances to modify data or trigger business logic.
- API endpoints
For each element, we define 4 levels of access: view, create, edit and remove.
Authentication implementations
The account component currently offers two standard implementations for authentication:
- Username-password authentication with built-in user management.
- OpenID Connect integration to use an external identity provider.
Features
Configuring authorization
When we use the base component Account for authorization, we define access by configuring the DataAccess data element.
OpenID Connect
The account component supports the use of OpenID Connect providers to authenticate in NS applications. Any provider can be used, as the implementation follows the OpenID Connect standard. The application will use the authorization code flow to authenticate the user. Only confidential clients (using clientid and clientsecret) with a code grant are supported.
Customizing authorization
Tasks