App metadata is cached per server

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 2.8.0.rc0
    • Affects Version/s: None
    • Component/s: Auth
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      We currently have app metadata cached per server, however the app metadata must be constructed per connection if the connection's credentials differ from the server's because the metadata is used for auth mechanism negotiation.

      This likely only affects the test suite and users who manually create connections (though fixing this should stop intermittent failures with scram/scram256 mismatch in our test suite).

            Assignee:
            Oleg Pudeyev (Inactive)
            Reporter:
            Oleg Pudeyev (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: