Failure to authenticate from web based interface

We are having trouble getting the web-based interface working.
We are running 24x7 Scheduler Multi-Platform edition on CentOS 5 linux.
Version 4.3 build 293

We are using jwi24x7.war under tomcat

When using PAM we get:
6-Dec-2009 09:38:28 PM 2 null null 24x7 Scheduler 24x7 Scheduler terminating...
6-Dec-2009 09:39:43 PM 2 null null 24x7 Scheduler 24x7 Scheduler starting...
6-Dec-2009 09:40:31 PM 2 null null 24x7 Scheduler User root connected from <XXX>
6-Dec-2009 09:40:32 PM 3 null null 24x7 Scheduler An error occurred during authentication. Module is unknown
6-Dec-2009 09:40:54 PM 2 null null 24x7 Scheduler User <user2> connected from <XXX>
6-Dec-2009 09:40:55 PM 3 null null 24x7 Scheduler An error occurred during authentication. Module is unknown

When switching to ftp I get:
6-Dec-2009 09:44:01 PM 2 null null 24x7 Scheduler User root connected from <XXX>
6-Dec-2009 09:44:02 PM 3 null null 24x7 Scheduler An error occurred during authentication. null
6-Dec-2009 09:44:10 PM 2 null null 24x7 Scheduler User <user2> connected from <XXX>
6-Dec-2009 09:44:10 PM 3 null null 24x7 Scheduler An error occurred during authentication. null

Can anyone help us?

Which user authentication method is currently selected in the scheduler settings? PAM or FTP?

Hi.
As I said above, when I tried PAM I got error 1 (module is unknown)
When I set FTP I got error 2 (An error occurred during authentication. null)

I have set it back to PAM now in Tools->Options->Security.

	Quote:
	when I tried PAM I got error 1 (module is unknown)

- this means that either the required Pluggable Authentication Module is not set on your system or you misconfigured pam.d. Did you copy ../pam/jscheduler file to your PAM configuration directory?. Please see section 6 in the readme.txt for info on how to configure PAM. This file is available 24x7 home directory.

	Quote:
	When I set FTP I got error 2 (An error occurred during authentication. null)

- Make sure local ftpd daemon is running.

Thanks!
Of course it makes sense now, it couldn't find the .so.
I tried with pam_unix.so but that was still giving the same problem.
Finally I copied a configuration from a known working pam as jscheduler and I was able to login. Hopefully there aren't any other consequences of that.

I am now able to login so we'll try it out.
Thanks again.

Thanks for the status update. Glad it's now working for you.