Updated TLS handshake timeout. #6692
Merged
Conversation
This file contains 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
r0mant
approved these changes
May 4, 2021
awly
approved these changes
May 4, 2021
Updated TLS handshake timeout. During some operations, Teleport can flood the network with traffic which causes the TLS handshake to occur slower than 1 second. One example is during SSO login. The initial connection is an unauthenticated connection, and upon successful SSO login a "types.User" is created and replicated to all nodes. For large clusters this can mean 10k+ "types.User" objects getting replicated at the same time the user attempts to re-establishing another connection to Auth this time with valid identity credentials. This connection sometimes can take longer than the original 1 second timeout.
russjones
force-pushed
the
rjones/update-timeouts
branch
from
846bc25
to
cc88d8a
Compare
This was referenced May 4, 2021
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Updated TLS handshake timeout. During some operations, Teleport can flood the network with traffic which causes the TLS handshake to occur slower than 1 second.
One example is during SSO login. The initial connection is an unauthenticated connection, and upon successful SSO login a "types.User" is created and replicated to all nodes. For large clusters this can mean 10k+ "types.User" objects getting replicated at the same time the user attempts to re-establishing another connection to Auth this time with valid identity credentials. This connection sometimes can take longer than the original 1 second timeout.