Open deusxanima opened 2 years ago
Circled back w/ end-user re: requirement for external MFA outside of Teleport-provided MFA. Response received is copied below:
With Teleport MFA we are trusting Teleport with MFA since a coding/config issue can disable/void the trigger (since it's all managed by teleport) With OS/PAM MFA when if Teleport is compromised, OS will still block and unauthorized access. That's the difference to us.
Description
What happened: Attempting to configure pam_yubico integration with teleport leads to all auth attempts failing when attempted through Teleport. Integration works fine, however, through standard OpenSSH. It appears that Teleport is injecting an extra byte or character which leads to pam_yubico module to swallow the first byte in order to fit the 12/32 token_id/otp expected response.
What you expected to happen: pam_yubico integration should work with teleport PAM auth.
Reproduction Steps
As minimally and precisely as possible, describe step-by-step how to reproduce the problem.
Server Details
teleport version
): 9.0.4/etc/os-release
): Ubuntu 20.04PAM Auth File:
PAM Auth File:
Client Details
tsh version
): 9.0.4Debug Logs
PAM Logs:
Teleport node logs:
gz#4642