Troubleshooting Password Management
Novell Cool Solutions: Tip
Digg This -
Posted: 6 Apr 2001
Current version: iChain 1.5
Here's how to avoid two common mistakes in the configuration of the Password Management Servlet.
If you're getting a 404 error when trying to use the Password Management Servlet, here's something to check.
The PasswordExpired.html starts a Java based Servlet whenever a user's password has expired, and a grace login is allowed. Since the code is written in java, it's case sensitive. If the ICS GUI configuration allowing configuration of the password management servlet does not include the correct cases, the 404 error message will be displayed as the file will not be found.
Make sure that the Password Management Servlet is configured with the following syntax:
For more information see TID 10060890
Check this out if your users are getting this kind of error when they try to change their password:
"Error in changing password - your password could not be changed. Please try again or contact your administrator."
This happens when the password management servlet is configured using the IP address, and not the hostname. The IP address inserted will be the IP address of the Web server where the servlet is running. When the user's password expires and he is prompted for the new password, the HTTP POST request will get sent to the Web server directly. When this happens, no NovellBMId cookie exists in the HTTP headers. The servlet tries to dereference the cookie, but doesn't find it and reports the message "Error in changing password - your password could not be changed. Please try again or contact your administrator." back to the browser.
Insert the hostname of the Web server so that the requests go through the Proxy server. This guarantees that the NovellBMId cookie is set in the forwarded request.
For more information see TID 10061024
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com