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

Audit log for provisioning user to a site is not working properly

      Issue Summary

      The audit log event "Synced user to site" is not reliable for newly provisioned accounts.

      This is reproducible on Data Center: no

      Steps to Reproduce

      1. Provision a new account into Atlassian cloud
      2. Go the organization audit logs
      3. Search for the "synced user to site" event related to the provisioned account.

      Expected Results

      An event should always be logged if a user was synced to the site via provisioning.

      Actual Results

      Sometimes it gets logged, sometimes it does not.

      Workaround

      Use the "Added user from identity provider" event instead as an indicator for the provisioning event.

            [ACCESS-1383] Audit log for provisioning user to a site is not working properly

            Anusha Rutnam made changes -
            Resolution New: Cannot Reproduce [ 5 ]
            Status Original: In Progress [ 3 ] New: Closed [ 6 ]
            cmac made changes -
            Component/s Original: Identity Internal - SCIM [ 56703 ]
            Component/s New: User Sync - SCIM Maintenance [ 66413 ]
            Key Original: ID-7960 New: ACCESS-1383
            Last Update On Original: 18/Aug/2022 [ 2022-08-18 ]
            Project Original: Identity [ 16810 ] New: Atlassian Access [ 18910 ]
            Anusha Rutnam made changes -
            Link New: This issue is related to JRACLOUD-79984 [ JRACLOUD-79984 ]
            Vagisha Tyagi made changes -
            Status Original: Needs Triage [ 10030 ] New: In Progress [ 3 ]
            Vagisha Tyagi made changes -
            Last Update On New: 18/Aug/2022 [ 2022-08-18 ]
            Status Original: Needs Triage [ 10030 ] New: Needs Triage [ 10030 ]
            Dilip Venkatesh made changes -
            Component/s Original: User Sync - SCIM Maintenance [ 66413 ]
            Component/s New: Identity Internal - SCIM [ 56703 ]
            Key Original: ACCESS-1251 New: ID-7960
            Project Original: Atlassian Access [ 18910 ] New: Identity [ 16810 ]
            SET Analytics Bot made changes -
            Support reference count New: 1
            Ramon M made changes -
            Description Original: h3. Issue Summary

            The audit log event "synced user to site" is not reliable for newly provisioned accounts.

            This is reproducible on Data Center: no

            h3. Steps to Reproduce
             # Provision a new account into Atlassian cloud
             # Go the organization audit logs
             # Search for the "synced user to site" event related to the provisioned account.

            h3. Expected Results

            An event should always be logged if a user was synced to the site via provisioning.

            h3. Actual Results

            Sometimes it gets logged, sometimes it does not.

            h3. Workaround

            Use the "Added user from identity provider" event instead as an indicator for the provisioning event.
            New: h3. Issue Summary
            The audit log event "Synced user to site" is not reliable for newly provisioned accounts.

            This is reproducible on Data Center: no

            h3. Steps to Reproduce
             # Provision a new account into Atlassian cloud
             # Go the organization audit logs
             # Search for the "synced user to site" event related to the provisioned account.

            h3. Expected Results

            An event should always be logged if a user was synced to the site via provisioning.

            h3. Actual Results

            Sometimes it gets logged, sometimes it does not.

            h3. Workaround

            Use the "Added user from identity provider" event instead as an indicator for the provisioning event.
            Ramon M created issue -

              Unassigned Unassigned
              rmacalinao Ramon M
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: