PAM error when connecting via an application

Criller · 11-07-2007, 08:40 AM

Hello,

Whenever I try to login to Redhat 4 via our ERP application I get the following errors.

2007-11-07[13:59:59]: Try authentication via PAM
2007-11-07[13:59:59]: PAM available for this platform
2007-11-07[13:59:59]: Authenticating user 'bsp'.
2007-11-07[13:59:59]: message 1: 'Password: '
2007-11-07[13:59:59]: Setting password for user bsp in PAM callback
2007-11-07[13:59:59]: Daemon: revert to listen-mode.
2007-11-07[14:00:01]: Failed to authenticate via PAM (error 28: Module is unknown)
2007-11-07[14:00:01]: No success via PAM; try classic route
2007-11-07[14:00:01]: Function HAL_cmp_password failed for user bsp
blogind6.1: Login failed for user bsp
2007-11-07[14:00:01]: Child: logon for bsp failed, pam Error: 28.

PAM unable to dlopen(/lib/security/added)
PAM [dlerror: /lib/security/added: cannot open shared object file: No such file or directory]
PAM adding faulty module: /lib/security/added

I have searched the great god google but cannt find anything relevant to my issue. Could somebody please elighten me as to what these errors may mean.

I have another Linux server set-up in the same way, or maybe not as the case may be that allows me to login without any issues.

Thanks

PJ

unSpawn · 11-11-2007, 05:58 AM

Quote:

Originally Posted by Criller

2007-11-07[14:00:01]: blogind6.1: Login failed for user bsp

Apparently you're running a commercial ERP (Baan). There is/was a Baanboard. Doesn't SSA Global do support? Before you go there I'd suggest you check the module references in your /etc/pam.d PAM stacks, turn on debugging and be able to present logs. Some PAM modules will take "debug" as argument and apparently blogind6.1 can be started with the "-d" flag to make it log debug info.

Criller · 11-20-2007, 06:18 AM

I've tried SSA, now Infor, support and they haven't got a clue. I have also tried Dell Redhat support, ditto.

The blogin6.1 does support the -d flag and the result of this are the errors I posted.

What I'm trying to find out is PAM module the blogind6.1 daemon is using. Under /etc/pam.d I cannot see anything that could be related to blogin.

Is there any other form of PAM debugging I can do, perhaps from a higher level which will the allow me to drill down to where the fault lies?

Thanks