Difference between revisions of "Common Security Troubleshooting"

Revision as of 09:52, 23 October 2007

This page contains exceptions that commonly occurs in security configurations for DILIGENT services. Exception should be clearly reported in sections using keywords as the Axis fault obtained, the error code returned by commands and so on (see already existing exceptions). For any exception a list of reasons can be reported as separate subsections. For each reason a solution should be also provided (if already discovered). To properly configure security for DILIGENT services please follows the How To Enable Security page.

GSI Secure Conversation authentication required for "{http://www...." operation

This exception tells the clients that the GSISecureConversation mechanism is required to acces the service client-config.wsdd must be correctly placed in your Apache Tomcat container. If you want to force axis to pick up your client-config.wsdd, you will have to place the client-config.wsdd in the tomcat-home/common/classes directory.

GSISecureConveration not set in service stubs

To access the service operation the GSISecureconversation must be set on client, please be sure to follows this documentation to set it correctly.

org.globus.wsrf.security.SecurityException: [SEC]Operation name could not be determined

Exception related to authentication of clients to a secure service running in the Java-WS-Core

voms-proxy-init error stream:Error: VERR_NOSOCKET

Exception related to authentication of clients to the VOMS server (ie. grids13.eng.it in this case) Contacting grids13.eng.it:15001 [/C=IT/O=INFN/OU=Host/L=ENGINEERING RDLAB/CN=grids13.eng.it] "diligent" Failed. Failed to contact servers for diligent.

Please doublecheck these settings:

• The clock on your computer could be not in sync with VOMS server. Use with ntp server Configure DHN security
• The CRLs has to be updated using /usr/sbin/fetch-crl -o /etc/grid-security/certificates
• Some CA certificates in /etc/grid-security/certificates could be expired, please update them.
• Your firewall or VOMS Server firewall blocks the client

Operation unauthorized (Mechanism level: Authorization failed. Expected "/CN=host/your_ip_number" target but received "/O=Grid/CN=host/your_hostname")

It is thrown when the hostname cannot be resolved asking the reverse DNS server. Usually this problem disappear as soon as the reverse DNS is updated.