Difference between revisions of "Common Security Troubleshooting"

From Gcube Wiki
Jump to: navigation, search
Line 1: Line 1:
 
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).
 
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 [[Security Training]] page.
 
To properly configure security for DILIGENT services please follows the [[Security Training]] 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
 +
 +
===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==
 
==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
 
Exception related to authentication of clients to a secure service running in the Java-WS-Core

Revision as of 12:34, 8 February 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 Security Training 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

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