-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Teleport Connect allow SSO hostname #48035
Conversation
This pull request is automatically being deployed by Amplify Hosting (learn more). |
lib/web/apiserver.go
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's the backward compatibility story going to look like here wrt SSO MFA? Do we run into a risk of Connect v17 wanting to use SSO MFA but not being able to because the proxy is on an older version which does not send SSOHostname
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
SSO MFA is being released in v17 so if we can get this in for v17.0.0 we won't have any issues.
Update Teleport Connect's proxy host allow list to allow opening an SSO provider's hostname.
When pinging the Teleport proxy for a specific connector, include the SSO hostname so it can be included in client-side logic determining whether a URL hostname should be trusted or not. This allow list logic only currently presides in Connect, but we may want to consider adding it to
tsh
andtctl
as well.Note: This change is necessary for SSO MFA to work in Connect, as Connect opens the URL within the context of the proxy host allow list.