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
Logging in with Github should correctly populate the addr.remote value with the user's external IP as seen by Teleport. This works correctly for OIDC, SAML and local user logins.
Current behavior
Any logins with a Github connector always seem to have the IP shown as 127.0.0.1.
In addition, the Github user.login event for contains a port number in addr.remote, whereas this is not present for OIDC or SAML login events. It is present for local login events, however, which is a further inconsistency.
Expected behavior
Logging in with Github should correctly populate the
addr.remote
value with the user's external IP as seen by Teleport. This works correctly for OIDC, SAML and local user logins.Current behavior
Any logins with a Github connector always seem to have the IP shown as
127.0.0.1
.In addition, the Github
user.login
event for contains a port number inaddr.remote
, whereas this is not present for OIDC or SAML login events. It is present for local login events, however, which is a further inconsistency.Logs
OIDC:
SAML:
Github:
Local:
Bug details:
The text was updated successfully, but these errors were encountered: