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

Update test projects so that we can toggle between RBAC and older auth modes

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 2.4.8
    • Fix Version/s: 2.5.0
    • Component/s: library
    • Labels:
      None

      Description

      Currently, all of the tests in Couchbase.IntegrationTests and most of what is in Couchbase.Test are setup to auth against pre-5.0 servers using the bucketname and password. All of these tests fail when run against CB 5.0 because of the changes to authentication because of RBAC.

      We need to come up with a way to toggle between bucketname/password and role-based authentication depending upon the cluster version/capabilities the tests are configured to run against.

        Attachments

          Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

            Activity

            Hide
            jmorris Jeff Morris added a comment -
            Show
            jmorris Jeff Morris added a comment - Michael Goldsmith - ideas?
            Hide
            mike.goldsmith Michael Goldsmith added a comment - - edited

            I think we need to work out the server version and optionally do auth differently if we're on 5.0+. This RFC was started to figure that out consistently across SDKs but there are concerns about working out feature availablity based on a number of factors (cluster version, hello flags, etc).

            I think NCBC-1443 should been seen as a prerequisite for this ticket, even if it just covers the server version which should be enough to determine if we need to auth with RBAC.

            Show
            mike.goldsmith Michael Goldsmith added a comment - - edited I think we need to work out the server version and optionally do auth differently if we're on 5.0+. This RFC  was started to figure that out consistently across SDKs but there are concerns about working out feature availablity based on a number of factors (cluster version, hello flags, etc). I think  NCBC-1443  should been seen as a prerequisite for this ticket, even if it just covers the server version which should be enough to determine if we need to auth with RBAC.
            Hide
            jmorris Jeff Morris added a comment -

            >>I think NCBC-1443 should been seen as a prerequisite for this ticket, even if it just covers the server version which should be >>enough to determine if we need to auth with RBAC.

            That is fine as long as were running all tests on Spock before we release 2.5.0 - coverage is the blocker.

            Show
            jmorris Jeff Morris added a comment - >>I think  NCBC-1443  should been seen as a prerequisite for this ticket, even if it just covers the server version which should be >>enough to determine if we need to auth with RBAC. That is fine as long as were running all tests on Spock before we release 2.5.0 - coverage is the blocker.
            Hide
            jmorris Jeff Morris added a comment - - edited

            Michael Goldsmith -

            I am going to start work on this by making an interim solution which toggles between auth modes via a config variable. NCBC-1479 can then pick up and automate the toggling via a server ping to determine the version/capabilities/etc. Then we will at least get test coverage for CB 5.0 and previous versions which use bucketname/password and not RBAC.

            For consistency, i will use a user with the name "myuser" and a password of "myuserpassword".

            Show
            jmorris Jeff Morris added a comment - - edited Michael Goldsmith - I am going to start work on this by making an interim solution which toggles between auth modes via a config variable. NCBC-1479 can then pick up and automate the toggling via a server ping to determine the version/capabilities/etc. Then we will at least get test coverage for CB 5.0 and previous versions which use bucketname/password and not RBAC. For consistency, i will use a user with the name "myuser" and a password of "myuserpassword".
            Hide
            jmorris Jeff Morris added a comment -

            Holding off on this ticket until NCBC-1443 is done.

            Show
            jmorris Jeff Morris added a comment - Holding off on this ticket until NCBC-1443 is done.
            Hide
            mike.goldsmith Michael Goldsmith added a comment -

            Unfortunately NCBC-1443 doesn't help here because you need to know if you need enhanced authentication before being able to query the Cluster Version on server 5.0. I'm looking into a config option that will tell use to do enhanced authentication.

            Show
            mike.goldsmith Michael Goldsmith added a comment - Unfortunately NCBC-1443 doesn't help here because you need to know if you need enhanced authentication before being able to query the Cluster Version on server 5.0. I'm looking into a config option that will tell use to do enhanced authentication.

              People

              • Assignee:
                mike.goldsmith Michael Goldsmith
                Reporter:
                jmorris Jeff Morris
              • Votes:
                0 Vote for this issue
                Watchers:
                3 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.