Skip to content

Client appears to not send token on connection request when user credentials are present #712

@glarrick757

Description

@glarrick757

Observed behavior

When attempting to connect via decentralized auth callout with both a token and user_credentials, the client appears to only pass the user_credentials.

Expected behavior

The connection request should include both the token and user_credentials.

Server and client version

Python Client Version: 2.10.0
Nats Server Version: 2.10.27

Host environment

No response

Steps to reproduce

  • Setup a NATS server with a decentralized auth callout service as described here
  • In the auth callout service, attempt to extract the token from incoming request claims
  • Using the python client, attempt to connect to the NATS server:
    nc, err := nats.Connect(
      "my_server_address",
      nats.UserCredentials("sentinel_creds"),
      nats.Token("my_secret_token")),
    )
  • Observe that the token extracted by the auth callout service is empty

Metadata

Metadata

Assignees

No one assigned

    Labels

    defectSuspected defect such as a bug or regression

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions