Closed nandan-bhat closed 4 months ago
Attention: Patch coverage is 85.36585%
with 12 lines
in your changes missing coverage. Please review.
Project coverage is 84.24%. Comparing base (
846c02c
) to head (1c70019
).
Files | Patch % | Lines |
---|---|---|
src/tools/auth0/handlers/scimHandler.ts | 84.21% | 5 Missing and 7 partials :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
🔧 Changes
In this PR, I'm adding a workaround to enable
SCIM
support onauth0-deploy-cli
with the currentnode-auth0@v3
version using the Auth0 Management API. This lets us useSCIM
features with the current SDK until we complete the migration tonode-auth0@v4
.scim_configuration
is added toconnections
scim_configuration
:user_id_attribute
,mapping
📚 References
🔬 Testing
Create a
config.json
file and keep it in the root of your project. Example:Make sure you have SCIM supported enterprise connections configured on your tenant. The currently the SCIM supported strategies are
samlp
,oidc
,okta
andwaad
Use the following commands to import or export configs: Export YAML:
node lib/index.js export -c config.json -o ./local -f yaml
Import YAML:node lib/index.js import -c config.json --input_file ./local/tenant.yaml
Refer documentationMake changes to
scim_configuration
insideconnections
and runimport
ordeploy
command. And observe the changes on your tenant.Navigate to
Authentication > Enterprise > [YOUR_SCIM_CONNECTION] > Provisioning
and make changes toSCIM
configuration. Run anyexport
ordump
command. Observe the changes on your local.📝 Checklist