Access problems after enabling security

 

Access problems after enabling security

 

+

Search Tips   |   Advanced Search

 

  1. Cannot access the administrative console or use the wsadmin tool after enabling security
  2. Cannot access a Web page after enabling security
  3. Authentication error accessing a Web page
  4. Authorization error accessing a Web page
  5. The client cannot access an enterprise bean after enabling security
  6. The client never gets prompted when accessing a secured enterprise bean
  7. Cannot stop an application server, node manager, or node after enabling security
  8. AccessControlException is reported in SystemOut.log
  9. After enabling SSO, cannot log on to the administrative console
  10. SECJ0306E: No received or invocation credential exists on the thread

See also:

  1. Troubleshoot the security component.
  2. Troubleshooting help from IBM

I cannot access all or part of the administrative console or use the wsadmin tool after enabling security

I cannot access a Web page after enabling securityWhen secured resources are not accessible, probable causes include:

The client cannot access an enterprise bean after enabling securityIf the client access to an enterprise bean fails after security is enabled:

If org.omg.CORBA.NO_PERMISSION exceptions occur when programmatically logging on to access a secured enterprise bean, an authentication exception has occurred on the server. Typically the CORBA exception is triggered by an underlying com.ibm.WebSphereSecurity.AuthenticationFailedException. To determine the actual cause of the authentication exception, examine the full trace stack:

  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)

A CORBA INITIALIZE exception with CWWSA1477W: SECURITY CLIENT/SERVER CONFIGURATION MISMATCH error embedded, is received by client program from the server. This error indicates that the security configuration for the server differs from the client in some fundamental way. The full exception message lists the specific mismatches. For example, the following exception lists three errors: 

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 general, resolving the problem requires a change to the security configuration of either the client or the server. To determine which configuration setting is involved, look at the text following the CWWSA error message. For more detailed explanations and instructions, look in the message reference, by selecting the Reference view of the information center navigation and expanding Messages in the navigation tree. In these particular cases:

Similarly, an exception like org.omg.CORBA.INITIALIZE: JSAS0477W: SECURITY CLIENT/SERVER CONFIG MISMATCH: appearing on the server trying to service a client request indicates a security configuration mismatch between client and server. The steps for resolving the problem are the same as for the JSAS1477W exceptions previously described.

Client program never gets prompted when accessing secured enterprise bean

Even though it seems that security is enabled and an enterprise bean is secured, occasions can occur when the client runs the remote method without prompting. If the remote method is protected, an authorization failure results. Otherwise, run the method as an unauthenticated user. Possible reasons for this problem include:

Cannot stop an application server, node manager, or node after enabling security

If you use command-line utilities to stop WebSphere Application Server processes, apply additional parameters after enabling security to provide authentication and authorization information.

Use the ./stopServer -help command to display the parameters to use. Use the following command options after enabling security:

If you use the Windows service panel or the net stop command to stop the WebSphere Application Server processes and the service could not be stopped, update the existing Application Server service using additional stop arguments. You might need to end the server process from the Task Manager before updating the service. Use the -stopArgs and the-encodeParams parameters to update the service as described in the "Updating an existing Application Server service" example in the WASService command article.

After enabling single sign-on, I cannot logon to the administrative console

This problem occurs when single sign-on (SSO) is enabled, and you attempt to access the administrative console using the short name of the server, for example http://myserver:port_number/ibm/console. The server accepts your user ID and password, but returns you to the logon page instead of the administrative console.

To correct this problem, use the fully qualified host name of the server, for example http://myserver.mynetwork.mycompany.com:9060/ibm/console.

The following exception displays in the SystemOut.log file after I start the server and enable security: "SECJ0306E: No received or invocation credential exists on the thread." The following message displays when one or more nodes within the cell was not synchronized during configuration: 

SECJ0306E: No received or invocation credential exists on the thread. The Role based 
authorization check will not have an accessId of the caller to check. The parameters 
are: access check method getServerConfig on resource FileTransferServer and module 
FileTransferServer. The stack trace is java.lang.Exception: Invocation and received 
credentials are both null.

Make sure that each of the nodes are synchronized and then restart the deployment manager.

 

Related tasks


Troubleshooting by component
Troubleshooting security configurations

Related reference

Errors after enabling security
WASService command

Searchable topic ID: rtrb_secprobs