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

Create a client mapper for the fhircore app id #190

Open
Wambere opened this issue May 22, 2024 · 1 comment
Open

Create a client mapper for the fhircore app id #190

Wambere opened this issue May 22, 2024 · 1 comment
Labels

Comments

@Wambere
Copy link
Contributor

Wambere commented May 22, 2024

When setting up keycloak using the importer, after creating users and assigning roles, we also need to create a mapper

Instructions taken from the FHIR InfoGateway Setup doc

Manual User Management
On Keycloak, one needs to:

  1. Create the users on Keycloak

  2. Assign the roles required for the user e.g. Provider/Practitioner, Supervisor

  3. Set up the fhir_core_app_id user attribute

    • Go to Users on Keycloak and select user
    • Click on Attributes tab
    • Enter the key as fhir_core_app_id
    • Enter the value as the corresponding user’s app id e.g. quest,cha
  4. Create a mapping to the JWT via a protocol mapper

    • Locate your FHIR Core Oauth client on Keycloak e.g. my-client
    • Click on the Client Scopes tab or Clients > Locate your fhir client > Edit > Select Mappers Tab > Create one from here
    • From the list look for an entry -dedicated and click on it
    • Click on the Mappers tab
    • Select Create/Configure a new mapper
    • Form the list select User Attribute
    • Give it a name e.g. FHIR Core App ID
    • Enter fhir_core_app_id for User Attribute and Token Claim name. These should match the key in the previous step.
    • Save the details
@pld
Copy link
Member

pld commented May 28, 2024

is this issue to do this automatically?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants