Unable to login to the web console

I am have installed the 24x7 scheduler and web console on RHEL:

Linux devdb04 2.6.9-5.ELsmp #1 SMP Wed Jan 5 19:29:47 EST 2005 x86_64 x86_64 x86_64 GNU/Linux

I can start the scheduler fine and the Java GUI. I am using PAM for authentication.

When I attempt to connect from the web console via Tomcat, I get Connection Denied! and the following error in the debug.log:

2007-06-22 19:59:18,476 [Thread-10171] DEBUG com.softtreetech.jscheduler.business.remotecontrol.SocketConnection - requestId 1
2007-06-22 19:59:18,477 [Thread-2] DEBUG com.softtreetech.jscheduler.business.remotecontrol.RemoteOperationsImpl - Connect called oracle _JAVA_ *****
2007-06-22 19:59:18,518 [Thread-10171] DEBUG com.softtreetech.jscheduler.business.remotecontrol.SocketConnection - requestId 3
2007-06-22 19:59:18,599 [Thread-10171] DEBUG com.softtreetech.jscheduler.business.remotecontrol.SocketConnection - requestId 6
2007-06-22 19:59:18,599 [Thread-10171] DEBUG com.softtreetech.jscheduler.business.remotecontrol.SocketConnection - Method name opensession
2007-06-22 19:59:18,599 [Thread-10171] DEBUG com.softtreetech.jscheduler.business.remotecontrol.SocketConnection - methodSignature LSSSS
2007-06-22 19:59:18,599 [Thread-10171] DEBUG com.softtreetech.jscheduler.business.remotecontrol.SocketConnection - arguments 4
2007-06-22 19:59:18,599 [Thread-10171] DEBUG com.softtreetech.jscheduler.business.remotecontrol.SocketConnection - method params [192.168.4.21, oracle, Welc0m3, *****]
2007-06-22 19:59:18,600 [Thread-3] DEBUG com.softtreetech.jscheduler.business.remotecontrol.RemoteOperationsImpl - Open session called 192.168.4.21 oracle Welc0m3
2007-06-22 19:59:18,600 [Thread-3] DEBUG com.softtreetech.jscheduler.business.runner.security.SecurityService - hasRemoteControlAccess: /u01/app/softtreetech/24x7/scheduler_242/rcontrol.pl
2007-06-22 19:59:18,612 [Thread-3] DEBUG com.softtreetech.jscheduler.business.runner.security.SecurityService - authNativeUser: /u01/app/softtreetech/24x7/scheduler_242/auth.pl
2007-06-22 19:59:18,624 [Thread-3] DEBUG com.softtreetech.jscheduler.business.runner.security.SecurityService -
2007-06-22 19:59:18,624 [Thread-3] ERROR com.softtreetech.jscheduler.business.remotecontrol.RemoteOperationsImpl - An error occurred during authentication
com.softtreetech.jscheduler.common.SchedException:
at com.softtreetech.jscheduler.business.runner.security.SecurityServiceImpl.hasRemoteControlAccess(Unknown Source)
at com.softtreetech.jscheduler.business.remotecontrol.RemoteOperationsImpl.openSession(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.softtreetech.jscheduler.business.remotecontrol.Request.run(Unknown Source)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: com.softtreetech.jscheduler.common.SchedException:
at com.softtreetech.jscheduler.business.runner.security.SecurityServiceImpl.authNativeUser(Unknown Source)
... 9 more
Caused by: com.softtreetech.jscheduler.common.SchedException:
... 10 more

Can anyone suggest what might be the cause of the problem?

from the log "An error occurred during authentication"

Which version of 24x7 are you running?
Do you have users configured in 24x7? Try deleting Users file and check if you can connect after that.

I'm using the Java version 4.1 build 242.

Deleting the users file does not seem to help - I still get the same error.

I suggest changing the settings in the scheduler to use FTP authentication just to verify if the PAM is configured properly. For FTP authentication to work, please ensure you have ftpd daemon running or have other FTP service enabled on the host. The scheduler will internally use that FTP service to authenticate users with the system and validate their passwords. If FTP authentication works then the issue is in PAM configuration, perhaps the 24x7 wasn't registered correctly with PAM or Perl-PAM module hasn't been installed. If it also doesn't work, then the problem is somewhere else.