-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Create user with single-factor authentication? #628
Comments
@jamesjuran2 perhaps |
That was the first thing I thought of, but the maximum time for --ttl is 1800 minutes, or 30 hours, which I recall seeing in the docs: [james.juran@localhost ~]$ tsh --proxy=teleport --ttl=1801 login If the 30 hour limit is arbitrary, I could make a local modification to set that considerably higher, but it would be nice to use the official releases. I also imagine I'm not the only one with this use case -- the automation I'm trying to run is Ansible, and I can't run Ansible from inside this cluster. |
@jamesjuran2 I'm thinking about it in the context of #620 - and it makes sense to add special permission property for some roles to sign certificates with longer TTLs. In this case you will be able to create |
Ok, I"ve updated section "TTL in certificates" to specifically address your concern. Closing this issue then. |
Is it possible to create a user that does not require two-factor authentication? My use case is I have automation running outside a Teleport cluster that I would like to log into the cluster periodically to perform a task. Because of the 2FA, I'll need to log into the server every day to re-auth with my 2FA token. In this particular case, the increased convenience of not having 2FA on this account is worth the security risk of someone compromising the stored single-factor credential.
The text was updated successfully, but these errors were encountered: