Make Keycloak's ID_KEY configurable #815
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.
Proposed changes
As explained in:
Currently, it is not possible to change the
ID_KEY
of the keycloak provider, even though this feature was meant to be present (according to the docstring). TheID_KEY
is basically the claim used to map a user.With this change, it is now possible to set the
ID_KEY
to any field present either in details or in the returned token:Types of changes
Please check the type of change your PR introduces:
Checklist
Put an
x
in the boxes that apply. You can also fill these out after creatingthe PR. If you're unsure about any of them, don't hesitate to ask. We're here to
help! This is simply a reminder of what we are going to look for before merging
your code.
Other information
I haven't added tests since such configurations don't seem to be tested on other backends. The default will stay exactly the same, thus not breaking the current behaviour.
Closes #813