Skip to content
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.

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

[Implement RBAC]: Role Based Access Control on FHIR web #1370

Closed
3 of 6 tasks
ageryck opened this issue Apr 8, 2024 · 2 comments
Closed
3 of 6 tasks

[Implement RBAC]: Role Based Access Control on FHIR web #1370

ageryck opened this issue Apr 8, 2024 · 2 comments
Labels
Feature Request Used to request for new features that are not available in the current application Needs Scoping Indicates that a ticket needs more scoping PharmAccess

Comments

@ageryck
Copy link
Contributor

ageryck commented Apr 8, 2024

Feature Use Case

Implement RBAC to allow users of the fhir web to only access and modify data based on assigned roles in keycloak.
CRUD operations roles are to be considered two resources consumed by fhir web, same backend implementation used by fhircore client applications can be used since we target to use the same gateway & keycloak deployment. The implementation should however be generic for users intending to deploy web with other IAM systems.

Acceptance criteria

  • web users assigned exclusive roles in keycloak
  • web users access filtered data based on assigned roles
  • web UI controlled by user roles

Project Contact

Ager

Relevant Information

RBAC has been scoped on this and this discussions. More web-specific scope to be provided

@ageryck ageryck added the Feature Request Used to request for new features that are not available in the current application label Apr 8, 2024
@ageryck ageryck added this to the Initial Run milestone Apr 8, 2024
@dubdabasoduba dubdabasoduba added the Needs Scoping Indicates that a ticket needs more scoping label Apr 12, 2024
@dubdabasoduba
Copy link
Member

Same as #1182

@pld
Copy link
Member

pld commented Jun 7, 2024

closing in favor of #1182 which has more details

@pld pld closed this as completed Jun 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request Used to request for new features that are not available in the current application Needs Scoping Indicates that a ticket needs more scoping PharmAccess
Projects
Status: Done
Development

No branches or pull requests

3 participants