-
Notifications
You must be signed in to change notification settings - Fork 157
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
Documentation on how to use Keycloak with FHIR #1546
Comments
I created the following blog post for this: https://github.com/Alvearie/alvearie.github.io/pull/35/files I'm not sure how much of that belongs in our repo vs just having somewhere to point to. Feedback welcomed. |
maybe a cross link would be just fine? |
TODO: replace current section of the user's guide with a link to keycloak extensions project. https://ibm.github.io/FHIR/guides/FHIRServerUsersGuide#53-openid-connect-and-oauth-20 |
1. Renamed jwtRP.xml to jwtRS.xml because the FHIR server is not technically a "Relying Party" but rather a JWT-based OAuth 2.0 Protected "Resource Server". 2. Removed disabled configDropins for configuring liberty as an OpenID Connect Provider / Consumer. Also removed the corresponding documentation as experience has shown that using an external Authorization Server together with the Liberty mpJwt feature has proven the most popular. 3. Introduce section 5.3.3 SMART App Launch to the User's Guide, including a reference to the [Alvearie Keycloak extensions for FHIR](https://github.com/Alvearie/keycloak-extensions-for-fhir) project and the [data-access](https://github.com/Alvearie/health-patterns/tree/main/data-access) pattern under Alvearie/health-patterns. Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
proposed updates for the user's guide: https://github.com/IBM/FHIR/blob/issue-1546/docs/src/pages/guides/FHIRServerUsersGuide.md |
1. Renamed jwtRP.xml to jwtRS.xml because the FHIR server is not technically a "Relying Party" but rather a JWT-based OAuth 2.0 Protected "Resource Server". 2. Removed disabled configDropins for configuring liberty as an OpenID Connect Provider / Consumer. Also removed the corresponding documentation as experience has shown that using an external Authorization Server together with the Liberty mpJwt feature has proven the most popular. 3. Introduce section 5.3.3 SMART App Launch to the User's Guide, including a reference to the [Alvearie Keycloak extensions for FHIR](https://github.com/Alvearie/keycloak-extensions-for-fhir) project and the [data-access](https://github.com/Alvearie/health-patterns/tree/main/data-access) pattern under Alvearie/health-patterns. Signed-off-by: Lee Surprenant <lmsurpre@us.ibm.com>
Signed-off-by: Troy Biesterfeld <tbieste@us.ibm.com>
Verified documentation in IBM FHIR Server Users Guide. |
Is your feature request related to a problem? Please describe.
Want to use Keycloak with FHIR server but don't know how.
Describe the solution you'd like
Provide documentation on how to use Keycloak with the FHIR server. For extra credit it would also include best practices and how to avoid pitfalls.
Also figure out where to store the output
Describe alternatives you've considered
n/a
Additional context
n/a
The text was updated successfully, but these errors were encountered: