Establish a register over end-user systems for a more user-friendly registration of system users. We will use the same postgre database defined #361
Results
Vendors can administrate the system types they provide in the market
End users can select system types when creating system users
You get a trusted source of system types
Get an understanding of what types of systems are used in Norway
Gives the possibility to create a consent-based onboarding of customers to the system providers
The register will contain a list of all relevant end-user systems.
The model for end-user system will be something like this.
{
"SystemTypeId": "visma_supertax",
"SystemVendor": "978234522",
"Name": {
"en": "Visma Super Tax",
"nb" : "Visma superskatt"
"Description": {
"en": "Visma Super Tax allows for .........",
"nb": "Visma superskatt gir deg mulighet...."
},
"AccessGroupNeeds": ["MVA", "SKATT"],
"ResourceNeeds": ["urn:altinn:resource:skd/mva"],.
"ClientId":["123123","234534552345"]
}
In scope
Registrering of systems (CRUD)
The solution should allow entities to register new end-user systems. This will be available as an API for the system vendors.
An API scope will control access to this API.
Listing of systems (LIST)
The UI for creating systems user will need a list of available systems.
Out of scope
Approval of system types
We will currently not add any approval of the system types. It needs to be clarified how this process should be and who should handle it. We have created a separate issue to define who can get access to scope #347
API owners would need to have a process for giving out scopes to the system vendors where they can approve it.
annerisbakk
commented
6 months ago
Description
Establish a register over end-user systems for a more user-friendly registration of system users. We will use the same postgre database defined #361
Results
The register will contain a list of all relevant end-user systems.
The model for end-user system will be something like this.
In scope
Registrering of systems (CRUD)
The solution should allow entities to register new end-user systems. This will be available as an API for the system vendors.
An API scope will control access to this API.
Listing of systems (LIST)
The UI for creating systems user will need a list of available systems.
Out of scope
Approval of system types
We will currently not add any approval of the system types. It needs to be clarified how this process should be and who should handle it. We have created a separate issue to define who can get access to scope #347
API owners would need to have a process for giving out scopes to the system vendors where they can approve it.
Additional Information
The data will be used from the following pages
https://github.com/Altinn/altinn-authentication-frontend/issues/19
https://github.com/Altinn/altinn-authentication-frontend/issues/17
The system register should probably get its own schema in the authentication database.
Tasks