Uploaded image for project: 'Sentry'
  1. Sentry
  2. SENTRY-2262

Sentry client is not compatible when connecting to Sentry 2.0

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.1.0
    • Fix Version/s: 2.1.0
    • Component/s: Sentry
    • Labels:
      None

      Description

      SENTRY-2162 added a new parameter 'entityName' in list_sentry_privileges_by_role() to replace the 'roleName' parameter. The change was propagated to the SentryPolicyServiceClientDefaultImpl to use the setEntityName(), but this is causing an incompatibility when connecting to a previous version of Sentry 2.0.

      The reason is that Sentry 2.0 does not accept an empty role name and it does not understand what entity name. To keep this compatibility, we need to still use the role name as a parameter in the client code for the rest of 2.x version until the roleName is removed in a major version of Sentry.

        Attachments

        1. SENTRY-2262.1.patch
          2 kB
          Sergio Peña
        2. SENTRY-2262.2.patch
          2 kB
          Sergio Peña

          Issue Links

            Activity

              People

              • Assignee:
                spena Sergio Peña
                Reporter:
                spena Sergio Peña
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: