Okta Advanced Server Access And Okta Privileged Access RDP Fails With Bad Certificate Error
Last Updated:
Overview
When attempting to establish a Remote Desktop Protocol (RDP) connection from a client to a Windows target server via Okta Advanced Server Access (ASA) or Okta Privileged Access (OPA), the connection fails with a bad certificate error. This occurs because the system time on the client and the target server are out of sync. Resolve this issue by synchronizing the clocks on both the client and the target server.
INFO Background client: Display modal error: title=RDP URL error body=rpc error: code = Unavailable desc = connection error: desc = "error reading server preface: remote error: tls: bad certificate
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Okta Advanced Server Access (ASA)
- Okta Privileged Access (OPA)
- Remote Desktop Protocol (RDP)
- Windows
Cause
The system time on the client and the target server are out of sync.
Solution
How is the bad certificate error resolved?
Synchronize the system clocks on the client and the target server to resolve the connection failure.
- Synchronize the time on the client machine with a reliable time source.
- Synchronize the time on the Windows target server with a reliable time source.
NOTE: Use Network Time Protocol (NTP) in the environment to automatically keep all server clocks synchronized.
