Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • 1
    The normal way to do what you describe would be to leave username/password authentication out of your module, and stack it after pam_unix (and pam_ldap). Commented Nov 14, 2014 at 22:28
  • I still want to be able to execute commands after the user has successfully authenticated themself. At first start, my module should detect that the user has not logged in previously, require an authentication and create my custom token afterwards. From the second login on I would not require pam_unix anymore (except when my module fails). Commented Nov 22, 2014 at 13:10