SALTO-4116: Support fetch and deploy for provisioning in apps #7003
+753
−10
Conversation
This file contains 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
idoamit8
force-pushed
the
SALTO-4116-SupportProvisioningForApps
branch
from
2d382f8 to
2ded985
Compare
idoamit8
force-pushed
the
SALTO-4116-SupportProvisioningForApps
branch
from
2ded985 to
9e86d66
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In this PR I support fetch and deploy for provisioning in apps
Additional context for reviewer
Some public APIs support User Provisioning (referred to as "ToApp" in the UI) and Inbound Provisioning (referred to as "To Okta" in the UI). These endpoints currently support a limited number of applications, as listed below:
match: ['^google$', '^office365$', '^okta_org2org$', '^slack$', '^zoomus$', '^zscalerbyz$']
Additionally, all applications have a private API that supports the To Okta page.
I plan to use the public API for the supported applications to enable both fetching and deploying their provisioning. For the remaining applications, I will support fetching and deploying only for what is represented by To Okta.
After first review I will add:
1. Tests
2. CV to say that we are not support enablement of provisioning (Although we will be able to support it if we turn off the CV (but its a mature of authentication)
Some screenshots:
Release Notes:
Replace me with a short sentence that describes the effect of this change on Salto users
User Notifications:
Replace me with a short sentence that describes changes that will appear in NaCls and are not caused by user actions (e.g. a new annotation, field values that are converted to references, etc). Hidden changes should not be listed.