Kbase P136009: Progress Explorer fails to start a database and generates a "User is not authenticated" error in the
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
3/8/2010 |
|
Status: Verified
SYMPTOM(s):
Progress Explorer fails to start a database running on a Solaris machine.
The adminserv.log file includes a "User not authenticated" error.
<log file entry> User is not authenticated. (9897)
root:Y:No Group Checking: User is not authenticated. (9897)
After setting the PSC_AUTH_DEBUG environment variable to get further debugging information from the admin server, the output fie created, authdbg.log, shows a "crypt failed" error:
IN validate_account root xxxxxx NULL
IN testUserPasswordForNull root xxxxxx
IN validatePassword root xxxxxx NULL
IN isGeneratedPassword = xxxxxxxx
IN validateUserPassword root xxxxxx
Calling getpwnam()
Calling getspnam()
Calling crypt()
crypt failed to set pStr
Return status of validate_account = 0
Progress Explorer can start the database after the root password is reset to the existing password, but only for the day that the password was reset. The next day, Progress Explorer fails to start the database.
FACT(s) (Environment):
The PSC_AUTH_DEBUG environment variable is set to yes to create authdbg.log debug file
/etc/policy.conf file has CRYPT_DEFAULT set to __UNIX__.
Sun Solaris SPARC
OpenEdge 10.1C
CHANGE:
/etc/policy.con file CRYPT_DEFAULT value changed from MD5 to __UNIX__.
CAUSE:
A script is run daily via a cron job that copies the /etc/passwd and /etc/shadow files from the main server to this clustered server. The /etc/shadow file is being replaced by the one on the main server where CRYPT_DEFAULT is still set to MD5 in the /etc/policy.conf file.
FIX:
Either remove that particular cron job (that copies the files) from the crontab, or change the CRYPT_DEFAULT value in the /etc/policy.conf file to __UNIX__ on the main server.