You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
We have upgraded our self-hosted boundary clusters in a K8s cluster from 0.11.0 to 0.13.1 by confirming there was no breaking changes at the CHANGELOG. Except for backing up the Postgres database, the upgrade workflow is as recommended here.
However, boundary is unable to establish the connections after the upgrade.
Proxy listening information:
Address: 127.0.0.1
Connection Limit: -1
Expiration: Tue, 09 Apr 2024 00:38:13 EDT
Port: 5432
Protocol: tcp
Session ID: s_KX2oDoXcn2
Session credentials were not accepted, or session is unauthorized
When searched for Session credentials were not accepted, or session is unauthorized error, I see that there are some github issues (#2257) related in the previous versions. As it made me think that it might be correlated to boundary cli version. I updated to the latest version (0.15.3) and it didn’t work and tried to using the same boundary cli version as the boundary cluster (0.13.1), but it didn’t help either.
Version information:
Build Date: 2023-07-14T13:03:00Z
Git Revision: db01791662a7126fbf4ea0a27b23b70acd20b17b
Version Number: 0.13.1
Describe the bug
We have upgraded our self-hosted boundary clusters in a K8s cluster from 0.11.0 to 0.13.1 by confirming there was no breaking changes at the CHANGELOG. Except for backing up the Postgres database, the upgrade workflow is as recommended here.
However, boundary is unable to establish the connections after the upgrade.
boundary connect -target-name=test-db-target --target-scope-name "Company Project" -listen-port 5432
Terminal Output:
When searched for Session credentials were not accepted, or session is unauthorized error, I see that there are some github issues (#2257) related in the previous versions. As it made me think that it might be correlated to boundary cli version. I updated to the latest version (0.15.3) and it didn’t work and tried to using the same boundary cli version as the boundary cluster (0.13.1), but it didn’t help either.
Extra infro that may help:
Controller Config:
Worker Config:
To Reproduce
Steps to reproduce the behavior:
v0.11.0
v0.13.1
as per the documentation (due to some deprecations we needed to upgrade the latest supported version for now)boundary connect -target-name=test-db-target --target-scope-name "Company Project" -listen-port 5432
Session credentials were not accepted, or session is unauthorized
Expected behavior
The session should be established successfully.
The text was updated successfully, but these errors were encountered: