Uploaded image for project: 'Atlassian Guard'
  1. Atlassian Guard
  2. ACCESS-2356

Make the SCIM error logs easily understandable

XMLWordPrintable

    • 1

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      At the moment, we see provisioning error logs for SCIM from time to time for different scenarios.

      For instance, when the SCIM data has been deleted for reasons like the deactivation of Atlassian Guard, and if IDP tries to resync data again after restoring the Guard subscription, we will find logs similar to below.
      Resource [USER] Missing user: <SCIM_ID>
      For our customer, this entry can be enhanced by adding additional details like the email. It would be great to add the context of where the user is missing. 

      In this case, the user is missing from the SCIM DB, hence we can't sync the user from SCIM to the Atlassian cloud

            [ACCESS-2356] Make the SCIM error logs easily understandable

            There are no comments yet on this issue.

              Unassigned Unassigned
              ab553f7c6d5e Sandip K Ghosh (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: