You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should make available a list of authorized parties over the EU API
Description
As of now, any Dialogporten consumer will have to make a separate integration to Access Management APIs in order to get valid values to put into Party. This is non-obvious, and a hinderance for adoption. Dialogporten will also need to intergrate this API in order to do search authorization, and will have this information cached. It therefore makes sense to expose a new endpoint over the EU API that can expose a custom DTO for authorized parties.
Considerations
Expose in GQL? Yes, included in PR.
Make available to SOs?
Implementation
This should use the same client and cache as will be required in #42. It is desirable for the consuming APIs to determine whether or not the current user has any special rights for each of the parties (key role, HADM ("hovedadministrator"), ADMAI ("tilgangsstyrer")), so that any GUI related to access management can rely on that information. Suggested DTO:
{"authorizedParties": [{"name": "NAVN PÅ AVGIVER","type": "Organization",// or "Person""identifier": "urn:altinn:organization:identifier-no::912345678","isDeleted": true,"hasKeyRole": true,"isMainAdmin": true,"isAccessManager": true,"subParties": [/* nullable, includes any nested parties */]},{"name": "NAVN PÅ AVGIVER","type": "Person",// or "Person""identifier": "urn:altinn:person:identifier-no::912345678","isDeleted": true,"hasKeyRole": true,"isMainAdmin": true,"isAccessManager": true}]}
The content you are editing has changed. Please copy your edits and refresh the page.
## Description
This adds a parties endpoint in the enduser-API, proxying requests to
access-management and returning a custom DTO for all parties that the
user has some sort of access relation to.
## Related Issue(s)
- #660
## Verification
- [x] **Your** code builds clean without any errors or warnings
- [x] Manual testing done (required)
- [x] Relevant automated test added (if you find this hard, leave it and
we'll help out)
## Documentation
- [ ] Documentation is updated (either in `docs`-directory, Altinnpedia
or a separate linked PR in
[altinn-studio-docs.](https://github.com/Altinn/altinn-studio-docs), if
applicable)
---------
Co-authored-by: Ole Jørgen Skogstad <skogstad@softis.net>
Introduction
We should make available a list of authorized parties over the EU API
Description
As of now, any Dialogporten consumer will have to make a separate integration to Access Management APIs in order to get valid values to put into
Party
. This is non-obvious, and a hinderance for adoption. Dialogporten will also need to intergrate this API in order to do search authorization, and will have this information cached. It therefore makes sense to expose a new endpoint over the EU API that can expose a custom DTO for authorized parties.Considerations
Implementation
This should use the same client and cache as will be required in #42. It is desirable for the consuming APIs to determine whether or not the current user has any special rights for each of the parties (key role, HADM ("hovedadministrator"), ADMAI ("tilgangsstyrer")), so that any GUI related to access management can rely on that information. Suggested DTO:
Tasks
The text was updated successfully, but these errors were encountered: