Role mapping across trusted clusters does not work if {{internal.logins}}
trait is the only one specified
#3402
Labels
Milestone
{{internal.logins}}
trait is the only one specified
#3402
What happened: Most of this issue is essentially a duplicate of #3376
The behaviour of
{{internal.logins}}
is broken in the same way as{{internal.kubernetes_groups}}
is - if you only specify{{internal.logins}}
and no other values on a role, logins do not get mapped correctly. If you add any other value at all, it works as expected.To clarify - this does not work:
This does work:
What you expected to happen: Logins should be correctly mapped across using the
{{internal.logins}}
field, regardless of other login values.How to reproduce it (as minimally and precisely as possible): See #3376 and Zendesk issue 1098.
Environment:
teleport version
):Teleport Enterprise v4.2.2git:v4.2.2-0-gb06a05d2 go1.13.2
tsh version
):Teleport v4.2.2 git:v4.2.2-0-gb06a05d2 go1.13.2
Fedora 30
The text was updated successfully, but these errors were encountered: