Skip to content

Update access control guidelines for standards selection #684

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mrtn78 wants to merge 1 commit into
base: master
Choose a base branch
from
+2 −1
Open

Update access control guidelines for standards selection #684

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion API-strategie-modules/access-control/access-control.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -364,7 +364,8 @@ The [Forum Standaardisatie Comply-Or-Explain-List](https://www.forumstandaardisa

The following guidelines should be used to select the appropriate standard for a specific context:

1. In the use case a User/Resource owner gives consent to a third-party to access Data
0. In the use case a citizen wants to login to a government service provider the service provider MUST provide a login service compatible with NL GOV Assurance Profile for OAuth 2.0
1. 1. In the use case a User/Resource owner gives consent to a third-party to access Data
* YES → NL GOV Assurance Profile for OAuth 2.0
* NO → go to 2
2. In the use case, data exchange occurs with General Digital Infrastructure (GDI) central systems (e.g., base registries), cross-sectoral between organizations, or requires mutual (two-way) authentication.
Expand Down
⚡