Uploaded image for project: 'Admin Experience'
  1. Admin Experience
  2. AX-295

If the user to be unsuspended does not have access to the license breached product, the unsuspend API should be allowed

    • 3
    • 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.

      Issue Summary

      If there is license breach in any organization. We cannot use the Restore user access API to unsuspend any user even if they do not consume the license of the license breached product.

      Suggestion

      If the user to be unsuspended does not have access to the license breached product, the unsuspend API should be allowed

      Workaround

      Unsuspend via the UI
      Resolve any license breached within the organization.

       

            [AX-295] If the user to be unsuspended does not have access to the license breached product, the unsuspend API should be allowed

            my new favorite admin error:
            "errors": [

            { "code": "ADMIN-400-32", "status": "400", "title": "TOO_MANY_LICENSE_BREACHES", "detail": "This operation cannot be processed as it modifies too many groups while a product license is breaching." }

            Mehmet Sari added a comment - my new favorite admin error: "errors": [ { "code": "ADMIN-400-32", "status": "400", "title": "TOO_MANY_LICENSE_BREACHES", "detail": "This operation cannot be processed as it modifies too many groups while a product license is breaching." }

            This is especially critical as the error message does not tell you which license is broken, so there is no chance for a quick fix.

            Instead, if a license is exceeded, a message to the ORG admins should be send, but no unannounced deactivation of a available/security-critical API functionality.

            Bruno Abele added a comment - This is especially critical as the error message does not tell you which license is broken, so there is no chance for a quick fix. Instead, if a license is exceeded, a message to the ORG admins should be send, but no unannounced deactivation of a available/security-critical API functionality.

              Unassigned Unassigned
              da47590cf79f Ishan Chaudhuri
              Votes:
              10 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: