Difference between revisions of "Security system errors and workarounds"

From GridPP Wiki
Jump to: navigation, search
(workaround for GSS error)
 
(typo)
Line 1: Line 1:
=Security system errors and workarounds. === Error in OLD GAA code: Could not get policy info: Minor status=201 ==
+
= Security system errors and workarounds === Error in OLD GAA code: Could not get policy info: Minor status=201 ==
  
 
Users at various sites have experienced strange error when using voms proxies to access grid services. The error manifests itself with the following message:  
 
Users at various sites have experienced strange error when using voms proxies to access grid services. The error manifests itself with the following message:  

Revision as of 12:23, 5 November 2015

Security system errors and workarounds === Error in OLD GAA code: Could not get policy info: Minor status=201 =

Users at various sites have experienced strange error when using voms proxies to access grid services. The error manifests itself with the following message:

ERROR: initializing context: GSS Error: GSS Major Status: Authentication Failed, MECH Error: GSS Minor Status Error 
Chain:, globus_gsi_gssapi: SSLv3 handshake problems, globus_gsi_callback_module: Could not verify 
credential, globus_gsi_callback_module: Error with signing policy, globus_gsi_callback_module: Error in OLD GAA code: 
Could not get policy info: Minor status=201 

Possible causes are suspected to include:

  • A bug in the globus_sgi_callback parser.
  • Clashes when GSS and CertWizard work with each other.
  • Non-standard shared directories and defaults

A workaround exists for this condition. On the user's system, check whether the user's ~/.globus directory is cluttered with various extraneous items. If so, strip back the content to usercert.* and userkey.* and try the operation again.