DaplaUserInfoMapper replace TeamsMapper #17
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Support for retrieving user, group and team info from Dapla Team API. Replaces the TeamsMapper.
Produces JSON claims, such as:
or (flat/non-nested)
Team and user properties to include are configurable. In addition, groups can be filtered by matching against a configurable regex, e.g. if you only want to include certain dapla groups such as developers. In that case, it is also configurable whether you want to only have teams with relevant groups or if all teams should be included.
Screenshot from the Keycloak Admin GUI:
This PR also adds a localstack setup that uses docker-compose to provide a local Keycloak instance that can be used for local development. It is very handy, essential even, to test the protocol mapper against a real Keycloak server.