Update SCIM provisioning requirements in documentation#11844
Update SCIM provisioning requirements in documentation#11844lorenyeung wants to merge 3 commits intoharness:mainfrom
Conversation
Clarified requirements for API key and permissions needed for SCIM provisioning in Harness.
Clarified requirements for OneLogin and Harness permissions, and recommended creating a separate service account for SCIM.
|
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://69afa1ba2e4a89a02eaf51d8--harness-developer.netlify.app |
|
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://69afa220bac0529bbd30b3e2--harness-developer.netlify.app |
|
Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://69afa236c37776873f86bbd4--harness-developer.netlify.app |
Clarified requirements for API key and permissions needed for SCIM provisioning in Harness.
Thanks for contributing to the Harness Developer Hub! Our code owners will review your submission.
Description
PR lifecycle
We aim to merge PRs within one week or less, but delays happen sometimes.
If your PR is open longer than two weeks without any human activity, please tag a code owner in a comment.
PRs must meet these requirements to be merged: