-
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
Expose --compat certificate flag to Web users #1542
Comments
We can extend the functionality we currently have in the
By default roles would have The Web UI would always use the compatibility value in the role, but with This would be backward compatible for existing users but also allow users to update how the Web UI requests certificates. @kontsevoy @klizhentas What do you think? |
this looks good to me |
How about:
This way in the docs I can say |
Talked about this with @kontsevoy offline, we'll change "compat" to "oldssh" so we can support multiple compatibility modes in the future. options:
cert_format: ["oldssh" | "standard"]
|
Problem
Older versions of OpenSSH have a bug which prevents them from consuming SSH certificates that contain metadata. For this purpose,
tsh login
uses--compat
flag to issue certificates that trade functionality (cross-cluster trust) for compatibility with oldersshd
.But when a Web UI user logs in, there's no equivalent to
--compat
option. This leads to web users not having access to legacysshd
hosts.Solution
TBD [by @klizhentas ] But one challenge I see is that it would be nice to make this work for open source users too, i.e. adding a role-hosted flag is not ideal.
The text was updated successfully, but these errors were encountered: