Access Denied for SSH showing unique id, not nodename #23719
Assignees
Labels
Comments
|
This has started occurring again. If the user puts in a non-allowed user they recieve this message with the node uuid.
|
rosstimothy
added a commit
that referenced
this issue
Oct 9, 2024
Host resolution no longer happens prior to connections in the Web UI and all dial attempts are by UUID. When an invalid login is attempted the error message constructed only contained the info provided to the dial request: a login and a Host UUID. To make this error more user friendly access denied errors are now augmented with the hostname if the user has permissions to that host and the error occurs only due to an invalid login. Closes #23719
|
@zmb3 is there any reason for the Web UI to allow users to input a custom login? Shouldn't all of the allowed logins be available in the dropdown list when clicking the connect button? Instead of allowing freeform text to be passed in for the login should that text input be converted to a filter for the available logins? |
rosstimothy
added a commit
that referenced
this issue
Oct 9, 2024
Host resolution no longer happens prior to connections in the Web UI and all dial attempts are by UUID. When an invalid login is attempted the error message constructed only contained the info provided to the dial request: a login and a Host UUID. To make this error more user friendly access denied errors are now augmented with the hostname if the user has permissions to that host and the error occurs only due to an invalid login. Closes #23719
You're correct. @avatus is actually working on removing the free form login entry for v17 right now. |
That's awesome. I'll proceed with a small tweak to improve the error messaging in <= v16 but won't attempt to introduce a more robust solution at this time then. |
github-merge-queue bot
pushed a commit
that referenced
this issue
Oct 15, 2024
) Host resolution no longer happens prior to connections in the Web UI and all dial attempts are by UUID. When an invalid login is attempted the error message constructed only contained the info provided to the dial request: a login and a Host UUID. To make this error more user friendly access denied errors are now augmented with the hostname if the user has permissions to that host and the error occurs only due to an invalid login. Closes #23719
github-actions bot
pushed a commit
that referenced
this issue
Oct 15, 2024
Host resolution no longer happens prior to connections in the Web UI and all dial attempts are by UUID. When an invalid login is attempted the error message constructed only contained the info provided to the dial request: a login and a Host UUID. To make this error more user friendly access denied errors are now augmented with the hostname if the user has permissions to that host and the error occurs only due to an invalid login. Closes #23719
github-actions bot
pushed a commit
that referenced
this issue
Oct 15, 2024
Host resolution no longer happens prior to connections in the Web UI and all dial attempts are by UUID. When an invalid login is attempted the error message constructed only contained the info provided to the dial request: a login and a Host UUID. To make this error more user friendly access denied errors are now augmented with the hostname if the user has permissions to that host and the error occurs only due to an invalid login. Closes #23719
rosstimothy
added a commit
that referenced
this issue
Oct 15, 2024
Host resolution no longer happens prior to connections in the Web UI and all dial attempts are by UUID. When an invalid login is attempted the error message constructed only contained the info provided to the dial request: a login and a Host UUID. To make this error more user friendly access denied errors are now augmented with the hostname if the user has permissions to that host and the error occurs only due to an invalid login. Closes #23719
rosstimothy
added a commit
that referenced
this issue
Oct 15, 2024
) Host resolution no longer happens prior to connections in the Web UI and all dial attempts are by UUID. When an invalid login is attempted the error message constructed only contained the info provided to the dial request: a login and a Host UUID. To make this error more user friendly access denied errors are now augmented with the hostname if the user has permissions to that host and the error occurs only due to an invalid login. Closes #23719
rosstimothy
added a commit
that referenced
this issue
Oct 15, 2024
) Host resolution no longer happens prior to connections in the Web UI and all dial attempts are by UUID. When an invalid login is attempted the error message constructed only contained the info provided to the dial request: a login and a Host UUID. To make this error more user friendly access denied errors are now augmented with the hostname if the user has permissions to that host and the error occurs only due to an invalid login. Closes #23719
rosstimothy
added a commit
that referenced
this issue
Oct 15, 2024
) Host resolution no longer happens prior to connections in the Web UI and all dial attempts are by UUID. When an invalid login is attempted the error message constructed only contained the info provided to the dial request: a login and a Host UUID. To make this error more user friendly access denied errors are now augmented with the hostname if the user has permissions to that host and the error occurs only due to an invalid login. Closes #23719
mvbrock
pushed a commit
that referenced
this issue
Oct 16, 2024
) Host resolution no longer happens prior to connections in the Web UI and all dial attempts are by UUID. When an invalid login is attempted the error message constructed only contained the info provided to the dial request: a login and a Host UUID. To make this error more user friendly access denied errors are now augmented with the hostname if the user has permissions to that host and the error occurs only due to an invalid login. Closes #23719
github-merge-queue bot
pushed a commit
that referenced
this issue
Oct 17, 2024
) Host resolution no longer happens prior to connections in the Web UI and all dial attempts are by UUID. When an invalid login is attempted the error message constructed only contained the info provided to the dial request: a login and a Host UUID. To make this error more user friendly access denied errors are now augmented with the hostname if the user has permissions to that host and the error occurs only due to an invalid login. Closes #23719
github-merge-queue bot
pushed a commit
that referenced
this issue
Oct 17, 2024
) (#47603) Host resolution no longer happens prior to connections in the Web UI and all dial attempts are by UUID. When an invalid login is attempted the error message constructed only contained the info provided to the dial request: a login and a Host UUID. To make this error more user friendly access denied errors are now augmented with the hostname if the user has permissions to that host and the error occurs only due to an invalid login. Closes #23719
github-merge-queue bot
pushed a commit
that referenced
this issue
Oct 17, 2024
) Host resolution no longer happens prior to connections in the Web UI and all dial attempts are by UUID. When an invalid login is attempted the error message constructed only contained the info provided to the dial request: a login and a Host UUID. To make this error more user friendly access denied errors are now augmented with the hostname if the user has permissions to that host and the error occurs only due to an invalid login. Closes #23719
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behavior:
The access denied shows the hostname, not the uuid.
Current behavior:
The access denied is showing the node unique id.
Bug details:
Connect to a ssh node with the wrong username in Web UI or Teleport Connect.
The text was updated successfully, but these errors were encountered: