Uploaded image for project: 'Couchbase .NET client library'
  1. Couchbase .NET client library
  2. NCBC-1444

Invalid error message when RBAC authentication fails

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 2.4.6
    • Fix Version/s: 2.5.0
    • Component/s: docs
    • Labels:
      None

      Description

      • if I specify correct user name and incorrect password I'm getting an error:
        "Authentication failed for bucket 'userName'"
      • I expected to see there a bucket name I was trying to open and perhaps something like
        "Authentication failed for user 'userName'"

        Attachments

        For Gerrit Dashboard: NCBC-1444
        # Subject Branch Project Status CR V

          Activity

          Hide
          mike.goldsmith Michael Goldsmith added a comment -

          Upon investigation it would not be possible to know whether the authentication type would be for a bucket or user until after this error is thrown. This is because the error occurs during ConnectionPoolBase.Authenticate and the client hasn't yet received a bucket config to determine bucket type.

          We could update the error message to be more ambiguous about authentication type, for example: "Authentication failed for bucket or username '{0}'" however we would be changing a potentially important error message that a customer may rely on for whatever reason.

          What do you think Jeff Morris?

          Show
          mike.goldsmith Michael Goldsmith added a comment - Upon investigation it would not be possible to know whether the authentication type would be for a bucket or user until after this error is thrown. This is because the error occurs during ConnectionPoolBase.Authenticate and the client hasn't yet received a bucket config to determine bucket type. We could update the error message to be more ambiguous about authentication type, for example: "Authentication failed for bucket or username '{0}'" however we would be changing a potentially important error message that a customer may rely on for whatever reason. What do you think Jeff Morris ?
          Hide
          jmorris Jeff Morris added a comment -

          That might be our only option...perhaps release note on 2.5.0?

          Show
          jmorris Jeff Morris added a comment - That might be our only option...perhaps release note on 2.5.0?
          Hide
          mike.goldsmith Michael Goldsmith added a comment -

          Yeah, I'd feel happier changing the error message on the 2.5.0 release with acompanying release notes. I'll update the ticket fix version.

          Show
          mike.goldsmith Michael Goldsmith added a comment - Yeah, I'd feel happier changing the error message on the 2.5.0 release with acompanying release notes. I'll update the ticket fix version.

            People

            • Assignee:
              jmorris Jeff Morris
              Reporter:
              jmorris Jeff Morris
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Gerrit Reviews

                There are no open Gerrit changes

                  PagerDuty

                  Error rendering 'com.pagerduty.jira-server-plugin:PagerDuty'. Please contact your Jira administrators.