Update field names and nav paths to reflect changes in newer Keycloak… #1641
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.
SURE-9548
Fixes #1114, fixes #1176
Description
Keycloak, including its docs, has undergone many revisions (e.g. new UI, migrated to Quarkus), which has caused a disconnect between what's indicated mentioned in our docs and what's in recent versions of Keycloak.
This PR updates references fields and navigation paths to sync with current versions (25/26) of Keycloak. Our existing docs list certain fields and their expected values, but newer Keycloak versions have additional fields (e.g.
lightweight access token
andAdd to token introspection
for the Group membership mapper type). Per engineering, these aren't used and can be left with the default value.I also opted to list out explicit Keycloak steps as I either couldn't find any relevant links or if linkable steps were present it needed additional context as the relevant steps were interwoven with other content.