Difference between revisions of "Common Security Troubleshooting"
From Gcube Wiki
| 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). | ||
| − | =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 11:12, 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).
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
