If you have to type a full DN at the login prompt, the user object probably does not reside under the container specified during iManager/Portal configuration. You need to run the Portal Servlet Configuration Wizard (http://your_iManager_server/nps/servlet/), and specify additional login containers for the contextless login. The Forgotten Password feature also uses this setting to resolve a user's DN.
If you see an error saying that a password policy is not assigned to a user from the Set Universal Password task, and you know that the user does have a password policy assigned, SSL might be the issue.
This can be a problem if you are running iManager on Windows 2000 machine with IIS as the Web server, because iManager install doesn’t automatically configure the certificate for you in that scenario.
Make sure that you are using a browser that iManager 2.02 supports.
When you set up iManager or one of Novell's portal products, such as exteNd™ Director™ Standard Edition, you specify the portal users container. Usually you specify a container at a high level in the tree, so that all users in the tree can access portal features. If all your users are below that container, then all users have access to Forgotten Password and Reset Password Self-Service.
If you later create a container with users outside the portal users' container, and these users can't access Forgotten Password and Reset Password features, you'll need to specifically assign rights to the following gadgets for that new container: Challenge Response Setup, Change Universal Password, and Hint Setup.
For instructions on adding new users to the portal users' container, see Portal User in the Novell exteNd Director Platform Edition Installation and Configuration Guide.
If you are installing Identity Manager in a multiserver environment and use some of the Password Management plug-ins in iManager, you might see an error that begins with NMAS LDAP Transport Error.
One common cause of this error is that the PortalServlet.properties file is pointing to an LDAP server that does not have the NMAS extensions that are needed for Identity Manager. Open the PortalServlet.properties file and make sure the address for the LDAP server is the same server where you installed Identity Manager.
Other possible causes: