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

Support additional filters (eq) for the user provisioning REST API

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.

      User Problem

      In certain scenarios, it is necessary to search for SCIM records that were provisioned without the userName and externalID attributes.

      Suggested Solutions

      In these situations, enabling the ability to filter the Get users SCIM REST API endpoint response using the SCIM record email (which serves as a unique identifier) instead of relying on the externalID or userName would significantly simplify the process of filtering results.

      Current Workarounds

      Currently, the only workaround is to retrieve the entire SCIM directory and manually parse the results to locate the specific attribute or use the Delete user in SCIM DB endpoint in cases where the SCIM record does not contain an externalID or Username and you want to delete this record

            [ACCESS-2153] Support additional filters (eq) for the user provisioning REST API

            Pablo Bastos made changes -
            Description Original: h3. User Problem

            In certain scenarios, it is necessary to search for SCIM records that were provisioned without the _userName_ and _externalID_ attributes.
            h3. Suggested Solutions

            In these situations, enabling the ability to filter the [Get users SCIM REST API|https://developer.atlassian.com/cloud/admin/user-provisioning/rest/api-group-users/#api-scim-directory-directoryid-users-get] endpoint response using the SCIM record _email_ (which serves as a unique identifier) instead of relying on the _externalID_ or _userName_ would significantly simplify the process of filtering results.
            h3. Current Workarounds

            Currently, the only workaround is to retrieve the entire SCIM directory and manually parse the results to locate the specific attribute or use the [Delete user in SCIM DB|https://developer.atlassian.com/cloud/admin/user-provisioning/rest/api-group-admin-apis/#api-admin-user-provisioning-v1-org-orgid-user-aaid-onlydeleteuserindb-delete] endpoint in cases where the SCIM record does not contain an externalID or Username             		New: h3. User Problem

            In certain scenarios, it is necessary to search for SCIM records that were provisioned without the _userName_ and _externalID_ attributes.
            h3. Suggested Solutions

            In these situations, enabling the ability to filter the [Get users SCIM REST API|https://developer.atlassian.com/cloud/admin/user-provisioning/rest/api-group-users/#api-scim-directory-directoryid-users-get] endpoint response using the SCIM record _email_ (which serves as a unique identifier) instead of relying on the _externalID_ or _userName_ would significantly simplify the process of filtering results.
            h3. Current Workarounds

            Currently, the only workaround is to retrieve the entire SCIM directory and manually parse the results to locate the specific attribute or use the [Delete user in SCIM DB|https://developer.atlassian.com/cloud/admin/user-provisioning/rest/api-group-admin-apis/#api-admin-user-provisioning-v1-org-orgid-user-aaid-onlydeleteuserindb-delete] endpoint in cases where the SCIM record does not contain an externalID or Username and you want to delete this record
            Pablo Bastos made changes -
            Description Original: h3. User Problem
            In certain scenarios, it is necessary to search for SCIM records that were provisioned without the _userName_ and _externalID_ attributes.

            h3. Suggested Solutions
            In these situations, enabling the ability to filter the [Get users SCIM REST API|https://developer.atlassian.com/cloud/admin/user-provisioning/rest/api-group-users/#api-scim-directory-directoryid-users-get] endpoint response using the SCIM record _email_ (which serves as a unique identifier) instead of relying on the _externalID_ or _userName_ would significantly simplify the process of filtering results.

            h3. Current Workarounds
            Currently, the only workaround is to retrieve the entire SCIM directory and manually parse the results to locate the specific attribute             		New: h3. User Problem

            In certain scenarios, it is necessary to search for SCIM records that were provisioned without the _userName_ and _externalID_ attributes.
            h3. Suggested Solutions

            In these situations, enabling the ability to filter the [Get users SCIM REST API|https://developer.atlassian.com/cloud/admin/user-provisioning/rest/api-group-users/#api-scim-directory-directoryid-users-get] endpoint response using the SCIM record _email_ (which serves as a unique identifier) instead of relying on the _externalID_ or _userName_ would significantly simplify the process of filtering results.
            h3. Current Workarounds

            Currently, the only workaround is to retrieve the entire SCIM directory and manually parse the results to locate the specific attribute or use the [Delete user in SCIM DB|https://developer.atlassian.com/cloud/admin/user-provisioning/rest/api-group-admin-apis/#api-admin-user-provisioning-v1-org-orgid-user-aaid-onlydeleteuserindb-delete] endpoint in cases where the SCIM record does not contain an externalID or Username
            SET Analytics Bot made changes -
            Support reference count New: 1
            Pablo Bastos created issue -

              2276519a4667 Ryan Van
              ca528a390f48 Pablo Bastos
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: