Login issues
The following sections highlight common login issues and their possible solutions.
File system is out of disk space.
Fully qualified URL incorrectly set up
URL not in the local hosts file or in DNS.
Domain incorrectly specified
Values in Tomcat Application Server and Apache Web Server do not match what's in DNS.
When a user can't log in to the Portal, the reasons are usually one of the following:
User forgot password. Change the user's password.
LDAP service is not running.
There is a port conflict. Another program is listening on port 80, resulting in a port conflict. Apache Web Server needs port 80. Use the netstat command to determine the other application that's listening on port 80, then assign that application a different port.
If Single Sign On (SSO) is not properly set up in the Admin>Advanced>System Configuration, after restarting you may not be able to log into the Portal. This utility resets the Single Sign On (SSO) parameters to provide Portal access. Run the following scripts from the command prompt:
Linux
cd /opt/aptare/utils ./resetSSOConfig.sh
Windows
cd C:\opt\aptare\utils resetSSOConfig.bat
Restart the Portal services after running the OS specific script.