Repository navigation
Session TTL capped by shortest role max_session_ttl; confusing "user does not exist" error in Connect after expiry #69919
|
Two questions about session TTL with several roles, and a confusing error when the session expires. Setup (Community Edition): proxy <>, 1. TTL across roles. As far as I can tell, the shortest 2. Error after the session expires. About an hour after login, Teleport Connect fails on database gateways with: It appears on Happy to open an issue if this is considered a bug. |
Replies: 1 comment 2 replies
|
1. TTL across roles. Yes. In the role reference, 2. The error after expiry. The text comes from the authorizer. So it follows from the current code rather than from a misconfiguration, and a clearer expired-session error with the re-login prompt would be a reasonable change to ask for. An issue is the right place for that. |
1. TTL across roles. Yes. In the role reference,
max_session_ttlis listed with the merge rule "The shortest TTL wins", so one 1h role caps every login of that user. There is no per-resource TTL inside a single login. Your plan fits the documented model: register each database twice withaccess=ro/access=rwlabels, scope the roles by label, and setrequire_session_mfa: trueon the rw role. In the per-session MFA guide ("Per role"), the option is set on a role and applies to what that role grants; each MFA check stays valid for up to 5 minutes, after which new connections ask again.mfa_verification_intervalis also listed as "shortest interval wins" in the role options table.2. The err…