teleport/docker/one.yaml
Sasha Klizhentas 83d0f7e7bb Fix role mapping for trusted clusters
This commit fixes #3252

Security patches 4.2 introduced a regression - leaf clusters ignore role mapping
and attempt to use role names coming from identity of the root cluster
whenever GetNodes method was used.

This commit reverts back the logic, however it ensures that the original
fix is preserved - traits and groups are updated on the user object.

Integration test has been extended to avoid the regression in the future.
2020-01-15 12:57:33 -08:00

40 lines
677 B
YAML

# Single-node Teleport cluster called "one" (runs all 3 roles: proxy, auth and node)
teleport:
nodename: one
advertise_ip: 172.10.1.1
log:
output: stdout
severity: DEBUG
data_dir: /var/lib/teleport
storage:
path: /var/lib/teleport/backend
type: dir
auth_service:
enabled: yes
authentication:
type: oidc
cluster_name: one
tokens:
- "node,auth,proxy:foo"
- "trustedcluster:bar"
ssh_service:
enabled: yes
labels:
cluster: one
commands:
- name: kernel
command: [/bin/uname, -r]
period: 5m
public_addr: ['localhost']
proxy_service:
enabled: yes
public_addr: ['localhost:3080']