feat: support custom group prefixes and filtering#388
Open
elaynelemos wants to merge 2 commits intodiscord:mainfrom
Open
feat: support custom group prefixes and filtering#388elaynelemos wants to merge 2 commits intodiscord:mainfrom
elaynelemos wants to merge 2 commits intodiscord:mainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
The following changes aim to make Access fit more use cases by adding customization layers to group operations.
Configurable group name prefixes (Resolves #382)
Group name prefixes for
OktaGroup,RoleGroup, andAppGroupwere previously hardcoded (Role-,App-), andOktaGrouphad no prefix support at all. These values are now configurable via theFRONTENDandBACKENDconfigs.Configurable Okta group sync filter (Resolves #385)
The Okta Groups API query parameters used when listing/syncing groups were previously hardcoded in
OktaServiceclass. They are now configurable viaDEFAULT_GROUP_QUERY_PARAMSin theBACKENDconfig, accepting any valid Okta Groups API query parameters as a JSON object. This allows restricting which groups are pulled and managed in Access.