-
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
Don't set logins directly from allowed logins for CertAuthority V2. #919
Conversation
917fb99
to
a77bb81
Compare
docker/README.md
Outdated
@@ -87,6 +87,37 @@ To setup Trusted Clusters: | |||
tctl -c /root/go/src/github.com/gravitational/teleport/docker/two-auth.yaml create -f docker/two-tc.yaml | |||
``` | |||
|
|||
#### Trusted Clusters with File Configuration | |||
|
|||
1. Export the CA for both clusters: |
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.
numbered lists don't look that good in the docs really, consider adding subtitles instead to separate sections
Export keys
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.
have a comment on the docs, otherwise lgtm
0e46849
to
7f19f6c
Compare
7f19f6c
to
c4f0b81
Compare
Purpose
As covered in #918, when you export CAs using the new style format, you will see the following in the Web UI:
The reason is because we were settings logins directly from allowed logins. This PR changes this behavior to match the behavior for how we parse CAs in the
known_hosts
format, we don't set logins directly but rather create a role first and add the role to the CertAuthority.Implementation
allowedLogins
.Related Issues
Fixes #918