Access problems after enabling security

• If you cannot access the administrative console, or view and update certain objects, look in the SystemOut log of the application server which hosts the administrative console page for a related error message.
• If you cannot access the administrative console, or view and update certain objects, look in the logs of the application server which hosts the administrative console page for a related error message.
  Note: You will need to use the administrative console to complete the next two items. If you are having a problem accessing the administrative console, you will have to turn off security and restart the administrative console. To turn off security, enter the following command at the system command prompt:

  wsadmin.sh -conntype NONE

  When the system command prompt displays again, enter:

  securityoff

  Restart the deployment manager after you turn off security.
• You might not have authorized your ID for administrative tasks. This problem is indicated by errors such as:
  • [8/2/02 10:36:49:722 CDT] 4365c0d9 RoleBasedAuth A CWSCJ0305A: Role based authorization check failed for security name MyServer/myUserId, accessId MyServer/S-1-5-21-882015564-4266526380-2569651501-1005 while invoking method getProcessType on resource Server and module Server.
  • Exception message: CWWMN0022E: Access denied for the getProcessType operation on Server MBean
  • When running the command: wsadmin -username j2ee -password j2ee: CWWAX7246E: Cannot establish "SOAP" connection to host "BIRKT20" because of an authentication failure. Ensure that user and password are correct on the command line or in a properties file.
  To grant an ID administrative authority, from the administrative console, click System Administration > Console Users and validate that the ID is a member. If the ID is not a member, add the ID with at least monitor access privileges, for read-only access.
• Verify that the trusted application functionality is enabled. The trusted application functionality is enabled if WebSphere Application Server has SAF access of READ to the RACF class of FACILITY, and profile of BBO.TRUSTEDAPPS.<cell short name>.<cluster short name>.

Remember: You could encounter synchronization problems if you are in a WebSphere Application Server Network Deployment environment and save your security settings and the node agent was down.

• Authentication errors - WebSphere Application Server security cannot identify the ID of the person or process. Symptoms of authentication errors include:
  On a Netscape browser:

  • Authorization failed. Retry? message is displayed after an attempt to log in.
  • Accepts any number of attempts to retry login and displays Error 401 message when Cancel is clicked to stop retry.
  • A typical browser message displays: Error 401: Basic realm='Default Realm'.
  On an Internet Explorer browser:

  • Login prompt displays again after an attempt to log in.
  • Allows three attempts to retry login.
  • Displays Error 401 message after three unsuccessful retries.
• Authorization errors - The security function has identified the requesting person or process as not authorized to access the secured resource. Symptoms of authorization errors include:
  • Netscape browser: Error 403: AuthorizationFailed message is displayed.
  • Internet Explorer:
    • You are not authorized to view this page message is displayed.
    • HTTP 403 Forbidden error is also displayed.
• SSL errors - WebSphere Application Server security uses Secure Sockets Layer (SSL) technology internally to secure and encrypt its own communication, and incorrect configuration of the internal SSL settings can cause problems. Also you might have enabled SSL encryption for your own web application or enterprise bean client traffic which, if configured incorrectly, can cause problems regardless of whether WebSphere Application Server security is enabled.
  • SSL-related problems are often indicated by error messages that contain a statement such as: ERROR: Could not get the initial context or unable to look up the starting context.Exiting. followed by javax.net.ssl.SSLHandshakeException

• Review the steps for securing and granting access to resources.

• Browse the server JVM logs for errors relating to enterprise bean access and security. Look up any errors in the message table.

  Browse the server logs for errors that relate to enterprise bean access and security. Look up any errors in the message table.

  Errors similar to Authorization failed for /UNAUTHENTICATED while invoking resource securityName:/UNAUTHENTICATED;accessId:UNAUTHENTICATED not granted any of the required roles roles indicate that:

  • An unprotected servlet or JavaServer Pages (JSP) file accessed a protected enterprise bean. When an unprotected servlet is accessed, the user is not prompted to log in and the servlet runs as UNAUTHENTICATED. When the servlet makes a call to an enterprise bean that is protected, the servlet fails.

    To resolve this problem, secure the servlet that is accessing the protected enterprise bean. Make sure that the runAs property for the servlet is set to an ID that can access the enterprise bean.

  • An unauthenticated Java client program is accessing an enterprise bean resource that is protected. This situation can happen if the file that is read by the sas.client.props properties file that is used by the client program does not have the securityEnabled flag set to true.

    To resolve this problem, make sure that the sas.client.props file on the client side has its securityEnabled flag set to true.

  Errors similar to Authorization failed for valid_user while invoking resource securityName:/username;accessId:xxxxxx not granted any of the required roles indicate that a client attempted to access a secured enterprise bean resource, and the supplied user ID is not assigned the required roles for that enterprise bean.

  • Check that the required roles for the enterprise bean resource are accessed. View the required roles for the enterprise bean resource in the deployment descriptor of the web resource.
  • Check the authorization table and make sure that the user or the group that the user belongs to is assigned one of the required roles. You can view the authorization table for the application that contains the enterprise bean resource using the administrative console.
• If you are using Local OS and System Authorization Facility (SAF) Authorization, check the SAF EJBROLEs setup. Specifically, verify that
  • the EJBROLE class is activated.
  • The role is defined to SAF.
  • The userid is permitted to the role.
  • The class is refreshed after the permit operation.

1. Begin by viewing the text following WSSecurityContext.acceptSecContext(), reason: in the exception. Typically, this text describes the failure without further analysis.
2. If this action does not describe the problem, look up the Common Object Request Broker Architecture (CORBA) minor code. The codes are listed in the article titled Troubleshooting the security components reference.
   For example, the following exception indicates a CORBA minor code of 49424300. The explanation of this error in the CORBA minor code table reads:

   authentication failed error

   In this case the user ID or password supplied by the client program is probably not valid:

   org.omg.CORBA.NO_PERMISSION: Caught WSSecurityContextException in 
   WSSecurityContext.acceptSecContext(), reason: Major Code[0] Minor Code[0] 
   Message[ Exception caught invoking authenticateBasicAuthData from SecurityServer 
   for user jdoe. Reason: com.ibm.WebSphereSecurity.AuthenticationFailedException] 
   minor code: 49424300 completed: 
   No at com.ibm.ISecurityLocalObjectBaseL13Impl.PrincipalAuthFailReason.map_auth_fail_to_minor_code 
   (PrincipalAuthFailReason.java:83)

Exception received: org.omg.CORBA.INITIALIZE: 
CWWSA1477W: SECURITY CLIENT/SERVER CONFIG MISMATCH: 
The client security configuration (sas.client.props or outbound settings in 
administrative console) does not support the server security configuration for 
the following reasons: 
ERROR 1: CWWSA0607E: The client requires SSL Confidentiality but the server does not 
         support it. 
ERROR 2: CWWSA0610E: The server requires SSL Integrity but the client does not 
         support it. 
ERROR 3: CWWSA0612E: The client requires client (e.g., userid/password or token), 
         but the server does not support it. 
     minor code: 0 
     completed: No at 
com.ibm.ISecurityLocalObjectBaseL13Impl.SecurityConnectionInterceptor.getConnectionKey
(SecurityConnectionInterceptor.java:1770)

• In ERROR 1, the client is requiring SSL confidentiality but the server does not support SSL confidentiality. Resolve this mismatch in one of two ways. Either update the server to support SSL confidentiality or update the client so that it no longer requires it.
• In ERROR 2, the server requires SSL integrity but the client does not support SSL integrity. Resolve this mismatch in one of two ways. Either update the server to support SSL integrity or update the client so that it no longer requires it.
• In ERROR 3, the client requires client authentication through a user id and password, but the server does not support this type of client authentication. Either the client or the server needs to change the configuration. To change the client configuration, modify the SAS.CLIENT.PROPS file for a pure client or change the outbound configuration for the server in the Security administrative console. To change the configuration for the target server, modify the inbound configuration in the Security administrative console.

• The server with which you are communicating might not have security enabled. Check with the WebSphere Application Server administrator to ensure that the server security is enabled. Access the security settings from within the Security section of the administrative console.
• The client does not have security enabled in the sas.client.props file. Edit the sas.client.props file to ensure the property com.ibm.CORBA.securityEnabled is set to true.
• The client does not have a ConfigURL specified. Verify that the property com.ibm.CORBA.ConfigURL is specified on the command line of the Java client, using the -D parameter.
• The specified ConfigURL does not have a valid URL syntax, or the sas.client.props that is pointed to cannot be found. Verify that the com.ibm.CORBA.ConfigURL property is valid. Check the Java documentation for a description of URL formatting rules. Also, validate that the file exists at the specified path.

  An example of a valid property is C:/WebSphere/AppServer/properties/sas.client.props.

• The client configuration does not support message layer client authentication (user ID and password). Verify that the sas.client.props file has one of the following properties set to true:
  • com.ibm.CSI.performClientAuthenticationSupported=true
  • com.ibm.CSI.performClientAuthenticationRequired=true
• The server configuration does not support message layer client authentication, which consists of a user ID and password. Check with the WebSphere Application Server administrator to verify that user ID and password authentication is specified for the inbound configuration of the server within the System Administration section of the administrative console administration tool.

• ./stopServer serverName -username name -password password
• ./stopNode -username name -password password
• ./stopManager -username name -password password