Now HOTP server checks 3 tokens ahead and syncs with client#39
Merged
alexlyulkov merged 1 commit intomasterfrom Oct 26, 2015
Merged
Now HOTP server checks 3 tokens ahead and syncs with client#39alexlyulkov merged 1 commit intomasterfrom
alexlyulkov merged 1 commit intomasterfrom
Conversation
Contributor
|
lgtm |
alexlyulkov
added a commit
that referenced
this pull request
Oct 26, 2015
Now HOTP server checks 3 tokens ahead and syncs with client
Joerger
added a commit
that referenced
this pull request
Sep 24, 2021
codingllama
added a commit
that referenced
this pull request
Nov 19, 2021
Removing the old roles migration allows Teleport to start even in the face of invalid roles. The system will still be largely unusable, but `tctl rm` is now possible as a fallback. Added logging makes it easier to determine the bad role. Turns this scenario: ```shell $ teleport start > (...) > ERROR: initialization failed > could not parse 'where' rule: "!contains(ssh_session.participants, user.metadata.name)", error: ssh_session.participants is not defined > (teleport exits) ``` into this: ```shell $ teleport start > (...) > 2021-11-18T16:50:29-03:00 WARN [AUTH:1:CA] "Re-init the cache on error: role \"join_own_sessions_only\"\n\tcould not parse 'where' rule: \"!contains(ssh_session.participants, user.metadata.name)\", error: ssh_session.participants is not defined." cache/cache.go:725 > 2021-11-18T16:50:29-03:00 WARN [AUTH:1:CA] Cache "auth" first init failed, continuing re-init attempts in background. error:[ > ERROR REPORT: > Original Error: *trace.BadParameterError could not parse 'where' rule: "!contains(ssh_session.participants, user.metadata.name)", error: ssh_session.participants is not defined > Stack Trace: > (...) > User Message: role "join_own_sessions_only" > could not parse 'where' rule: "!contains(ssh_session.participants, user.metadata.name)", error: ssh_session.participants is not defined] cache/cache.go:678 > 2021-11-18T16:50:35-03:00 WARN [AUTH:1:CA] "Re-init the cache on error: role \"join_own_sessions_only\"\n\tcould not parse 'where' rule: \"!contains(ssh_session.participants, user.metadata.name)\", error: ssh_session.participants is not defined." cache/cache.go:725 > (teleport running, tctl works) ``` See #9059 for the larger context. * Remove Teleport 4.3 role migration * Remove unused parameters * Add role name to GetRoles validation failures
codingllama
added a commit
that referenced
this pull request
Nov 23, 2021
Removing the old roles migration allows Teleport to start even in the face of invalid roles. The system will still be largely unusable, but `tctl rm` is now possible as a fallback. Added logging makes it easier to determine the bad role. Turns this scenario: ```shell $ teleport start > (...) > ERROR: initialization failed > could not parse 'where' rule: "!contains(ssh_session.participants, user.metadata.name)", error: ssh_session.participants is not defined > (teleport exits) ``` into this: ```shell $ teleport start > (...) > 2021-11-18T16:50:29-03:00 WARN [AUTH:1:CA] "Re-init the cache on error: role \"join_own_sessions_only\"\n\tcould not parse 'where' rule: \"!contains(ssh_session.participants, user.metadata.name)\", error: ssh_session.participants is not defined." cache/cache.go:725 > 2021-11-18T16:50:29-03:00 WARN [AUTH:1:CA] Cache "auth" first init failed, continuing re-init attempts in background. error:[ > ERROR REPORT: > Original Error: *trace.BadParameterError could not parse 'where' rule: "!contains(ssh_session.participants, user.metadata.name)", error: ssh_session.participants is not defined > Stack Trace: > (...) > User Message: role "join_own_sessions_only" > could not parse 'where' rule: "!contains(ssh_session.participants, user.metadata.name)", error: ssh_session.participants is not defined] cache/cache.go:678 > 2021-11-18T16:50:35-03:00 WARN [AUTH:1:CA] "Re-init the cache on error: role \"join_own_sessions_only\"\n\tcould not parse 'where' rule: \"!contains(ssh_session.participants, user.metadata.name)\", error: ssh_session.participants is not defined." cache/cache.go:725 > (teleport running, tctl works) ``` See #9059 for the larger context. * Remove Teleport 4.3 role migration * Remove unused parameters * Add role name to GetRoles validation failures
codingllama
added a commit
that referenced
this pull request
Nov 23, 2021
Removing the old roles migration allows Teleport to start even in the face of invalid roles. The system will still be largely unusable, but `tctl rm` is now possible as a fallback. Added logging makes it easier to determine the bad role. Turns this scenario: ```shell $ teleport start > (...) > ERROR: initialization failed > could not parse 'where' rule: "!contains(ssh_session.participants, user.metadata.name)", error: ssh_session.participants is not defined > (teleport exits) ``` into this: ```shell $ teleport start > (...) > 2021-11-18T16:50:29-03:00 WARN [AUTH:1:CA] "Re-init the cache on error: role \"join_own_sessions_only\"\n\tcould not parse 'where' rule: \"!contains(ssh_session.participants, user.metadata.name)\", error: ssh_session.participants is not defined." cache/cache.go:725 > 2021-11-18T16:50:29-03:00 WARN [AUTH:1:CA] Cache "auth" first init failed, continuing re-init attempts in background. error:[ > ERROR REPORT: > Original Error: *trace.BadParameterError could not parse 'where' rule: "!contains(ssh_session.participants, user.metadata.name)", error: ssh_session.participants is not defined > Stack Trace: > (...) > User Message: role "join_own_sessions_only" > could not parse 'where' rule: "!contains(ssh_session.participants, user.metadata.name)", error: ssh_session.participants is not defined] cache/cache.go:678 > 2021-11-18T16:50:35-03:00 WARN [AUTH:1:CA] "Re-init the cache on error: role \"join_own_sessions_only\"\n\tcould not parse 'where' rule: \"!contains(ssh_session.participants, user.metadata.name)\", error: ssh_session.participants is not defined." cache/cache.go:725 > (teleport running, tctl works) ``` See #9059 for the larger context. * Remove Teleport 4.3 role migration * Remove unused parameters * Add role name to GetRoles validation failures
hatched
pushed a commit
to hatched/teleport-merge
that referenced
this pull request
Nov 30, 2022
nick-inkeep
pushed a commit
to nick-inkeep/teleport-docs
that referenced
this pull request
Jun 20, 2023
…sign-in Fix sign-in dropdown
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.