Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[v14] docs: mention security tools that break mTLS with LDAP #40502

Merged
merged 1 commit into from
Apr 12, 2024
Merged

[v14] docs: mention security tools that break mTLS with LDAP #40502

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/cspell.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -185,6 +185,7 @@
"SUNSUBSCRIBE",
"SUPATH",
"Shockbyte",
"Silverfort's",
"Slackbot",
"Sllavd",
"Smartcard",
Expand Down
10 changes: 8 additions & 2 deletions docs/pages/desktop-access/troubleshooting.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,7 +81,7 @@ If your group policy prevents the desktop from seeing this PIN, the user will
remain at the login screen even though the smart card was detected.

**Solution:** Ensure that group policy allows specifying credentials during
RDP connection establishment.
RDP connection establishment.

Expand Computer Configuration, Administrative Templates, Windows Components,
Remote Desktop Services, and Remote Desktop Session Host.
Expand Down Expand Up @@ -177,7 +177,7 @@ or
connecting to LDAP server: unable to read LDAP response packet: read tcp 172.18.0.5:35970->;172.18.0.4:636: read: connection reset by peer
```

**Solution:** Enable LDAPS
**Solution:** Enable LDAPS

This means you do not have an LDAP certificate installed on your LDAP servers,
or you are trying to make an insecure connection on port `389`. Teleport requires
Expand Down Expand Up @@ -239,6 +239,12 @@ in LDAP, you can force the desktop to sync with the following command:
$ certutil -pulse
```

If you have verified that the Teleport CA certificate is properly installed and
are still seeing this error, check for any security tools or addons that may be
interfering with the mTLS connection. Tools such as CrowdStrike's LDAP inspection
or Silverfort's AD adapter are known to terminate TLS and drop the client certificate,
which prevents Teleport from authenticating.

## Connection attempts fail

### RDP server only uses Standard RDP Security
Expand Down
Loading