Non-interactive ssh sessions and CLI tool creation about duo_unix HOT 4 CLOSED

The non-interactive method would also be useful for Continuous Integration scenarios.
Currently we bake all our EC2: AMIs through Wercker, using Packer as a tool within the wercker box.

However as all provisioning happens through a user account unassociated with a duo identity (not being a person it lacks a phone number to push OTP to), CI bakes broke once we switched from login_duo to pam_duo. A non interactive implementation would help this scenario.

from duo_unix.

@Hashfyre Since you say the user doesn't have a Duo account, it doesn't sound like a non-interactive 2fa wouldn't fix your use case. Does the 'groups' configuration option help you? It allows some user accounts to bypass Duo, based on group membership of the account.

from duo_unix.

@malandrew Sorry for not responding to your issue, it fell off of our radar. In the future, please feel free to contact [email protected], where we have processes in place to ensure requests are captured and tracked.

Have you tried the 'autopush' configuration feature of duo unix? It may address your use case.

Thanks for using Duo!

from duo_unix.

Closing out this old issue

from duo_unix.