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.

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

Jump to bottom

[Maintenance] Keycloak custom mappers #258

Open
2 tasks done
devtobi opened this issue Aug 29, 2024 · 1 comment · May be fixed by #632
Open
2 tasks done

[Maintenance] Keycloak custom mappers #258

devtobi opened this issue Aug 29, 2024 · 1 comment · May be fixed by #632
Labels
Priority: Medium The issue contains work with medium priority. Type: Maintenance The issue contains maintenance work.
Milestone
Q1

Comments

@devtobi
Copy link
Member

devtobi commented Aug 29, 2024

Relevant template

No response

Problem description (optional)

Currently our user object in refarch/frontend/types/User.ts contains lots of metadata which come from our internal SSO provider. However we should modify our local keycloak stack to provide this data as well (dummy data).
Missing information in the local stack will lead to errors in the frontend, because User object cannot be constructed safely.

Desired solution

Modify the local keycloak stack to reproduce our company internal user information.

Considered alternatives (optional)

No response

Additional context (optional)

No response

No duplicate

  • I confirm that this issue is not a duplicate

Code of Conduct

  • I agree to follow this project's Code of Conduct
@devtobi devtobi added Type: Maintenance The issue contains maintenance work. Priority: High The issue contains work with high priority. labels Aug 29, 2024
@devtobi devtobi added Priority: Medium The issue contains work with medium priority. and removed Priority: High The issue contains work with high priority. labels Nov 7, 2024
@devtobi devtobi mentioned this issue Nov 7, 2024
Open
2 tasks
@simonhir simonhir mentioned this issue Nov 22, 2024
Open
2 tasks
@eidottermihi
Copy link
Member

I have done this in an internal project, especially the claims provided by scopes LHM (e.g. lhmObjectID) and LHM_Extended should be "mocked" / provided with dummy data from the "stack keycloak".

Examples:

Documentation for LHM specific scopes (internal): https://wiki.muenchen.de/betriebshandbuch/wiki/Red_Hat_Single_Sign-On_(Keycloak)#Scopes

@DanielOber DanielOber added this to the Q1 milestone Dec 6, 2024
@eidottermihi eidottermihi linked a pull request Dec 9, 2024 that will close this issue
Open
@eidottermihi eidottermihi linked a pull request Dec 9, 2024 that will close this issue
Add custom LHM Keycloak scopes #632
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Priority: Medium The issue contains work with medium priority. Type: Maintenance The issue contains maintenance work.
Projects
it@M RefArch Templates
Status: Blocked
Milestone
Q1
Development

Successfully merging a pull request may close this issue.

Add custom LHM Keycloak scopes it-at-m/refarch-templates
3 participants
@eidottermihi @devtobi @DanielOber