Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-0603: "at" commands may not work for AD Users on SuSE10

Centrify DirectControl ,  

12 April,16 at 11:27 AM

Problem:

"at" commands may not work for AD Users on SuSE10. When trying to run "at" commands as an AD user gets the following error:
"PAM authentication failure: Authentication token is no longer valid; new one required. You do not have permission to use at."

But if you turn on debugging for Centrify agent, the corresponding log message for the above error is:
at[8539]: WARN pam Account management for user 'shipper': password has expired"


Reason:

"at" commands on SuSE10 do make calls to PAM but "at" make a call "setreuid(25) (where 25 is daemon user for "at") before calling pam_acct_mgmt which is wrong. On platforms where it works such as RHEL4, "at" does setreuid(0) before calling pam_acct_mgmt.


Resolution:

This behavior is not as a result of Centrify DirectControl agent but because of a bug in "at". Centrify tried to open a bug with the original author of "at" but were unsuccessful. "at" can be fixed by creating an RPM that changes the setreuid to 0. Few customers also confirmed that by doing so it works.

Still have questions? Click here to log a technical support case, or collaborate with your peers in Centrify's Online Community.