-
Suggestion
-
Resolution: Unresolved
-
2
-
Use Case : Some automation require users and groups data to be provisioned via SCIM and used for creating Confluence spaces or Jira projects.
- Provision a user or group via SCIM API
- Immediately reference the user or group in a Jira, Confluence or User Management API.
This will fail because the provisioned user or group data needs to propagate first to the site before it can be utilize by Jira, Confluence or User Management API.
Suggestion :
Allow the Jira, Confluence and User Management API to be able to reference immediately the user or group data that has been provisioned via SCIM (ie. check the SCIM directory and pull the latest user and group data)
Workaround :
Wait for the user and group data to propagate and re-try the Jira, Confluence or User Management API call
- relates to
-
CONFCLOUD-77359 Allow provisioned users and groups to be immediately available for API usage
- Gathering Interest
-
JRACLOUD-82751 Allow provisioned users and groups to be immediately available for API usage
- Gathering Interest
-
ENT-1936 Loading...
[ID-8482] Allow provisioned users and groups to be immediately available for API usage
Labels | New: guard-s7 |
Support reference count | Original: 1 | New: 2 |
Support reference count | New: 1 |
Remote Link | Original: This issue links to "ENT-1936 (Jira)" [ 856695 ] | New: This issue links to "ENT-1936 (Hello Jira)" [ 856695 ] |
Remote Link | New: This issue links to "ENT-1936 (Jira)" [ 856695 ] |
Link | New: This issue relates to JRACLOUD-82751 [ JRACLOUD-82751 ] |
Link | Original: This issue was cloned as CONFCLOUD-77359 [ CONFCLOUD-77359 ] |
Link | New: This issue relates to CONFCLOUD-77359 [ CONFCLOUD-77359 ] |
Description |
Original:
Use Case : Some automation require users and groups data to be provisioned via SCIM and used for creating Confluence spaces or Jira projects.
- Provision a user or group via SCIM API - Immediately reference the user or group in a Jira, Confluence or User Management API. This will fail because the provisioned user or group data needs to propagate first to the site before it can be utilize by Jira, Confluence or User Management API. Suggestion : Allow the Jira, Confluence and User Management API to be able to reference immediately the user or group data that has been provisioned via SCIM (ie. check the SCIM directory and pull the latest user and group data) Workaround : Wait for the user and group data to propagate and re-try the Jira, Confluence or User Management API call |
New:
*Use Case* : Some automation require users and groups data to be provisioned via SCIM and used for creating Confluence spaces or Jira projects.
- Provision a user or group via SCIM API - Immediately reference the user or group in a Jira, Confluence or User Management API. This will fail because the provisioned user or group data needs to propagate first to the site before it can be utilize by Jira, Confluence or User Management API. *Suggestion* : Allow the Jira, Confluence and User Management API to be able to reference immediately the user or group data that has been provisioned via SCIM (ie. check the SCIM directory and pull the latest user and group data) *Workaround* : Wait for the user and group data to propagate and re-try the Jira, Confluence or User Management API call |