What kind of error are you seeing?
Authentication error accessing a Web page
Possible causes for authentication errors include:
Authorization error accessing a Web page
If a user who should have access to a resource does not, there is probably a missing configuration step. Review the steps for securing and granting access to resources.
Specifically:
Error Message: SECJ0314E: Current Java 2 security policy reported a potential violation on server
If you find errors on your server similar to:
Error Message: SECJ0314E: Current Java 2 Security policy reported a potential violation of Java 2 Security Permission. Please refer to Problem Determination Guide for further information. {0}Permission\:{1}Code\:{2}{3}Stack Trace\:{4}Code Base Location\:{5}The Java security manager checkPermission() method has reported an exception, SecurityException.
The reported exception might be critical to the secure system. Turn on security trace to determine the potential code that might have violated the security policy. Once the violating code is determined, verify if the attempted operation is permitted with respect to Java 2 Security, by examining all applicable Java 2 security policy files and the application code.
A more detailed report is enabled by either configuring RAS trace into debug mode, or specifying a Java property.
For a review of Java security policies and what they mean , see the Java 2 Security documentation at http://java.sun.com/j2se/1.3/docs/guide/security/index.html .
Tip: If the application is running with a Java Mail API, this message might be benign. You can update the installed Enterprise Application root/META-INF/was.policy file to grant the following permissions to the application:
Error message: MSGS0508E: The JMS Server security service was unable to authenticate user ID
This error can result from installing the JMS messaging API sample and then enabling security. You can follow the instructions in the Configure and Run page of the corresponding JMS sample documentation to configure the sample to work with WebSphere Application Server security.
You can verify the installation of the message-driven bean sample by launching the installation program, selecting Custom, and browsing the components which are already installed in the Select the features you like to install panel. The JMS sample is shown as Message-Driven Bean Sample, under Embedded Messaging.
You can also verify this installation by using the administrative console to open the properties of the application server which contains the samples. Select MDBSamples and click uninstall.
Error message: SECJ0237E: One or more vital LTPAServerObject configuration attributes are null or not available after enabling security and starting the application server.
This error message can result from selecting LTPA as the authentication mechanism, but not generating the LTPA keys. The LTPA keys encrypt the LTPA token.
To resolve this problem:
Error Message: SECJ0336E: Authentication failed for user {0} because of the following exception {1}
This error message results if the user ID indicated is not found in the LDAP user registry. To resolve this problem: