We are using WSGRAM v4.0.6 to submit jobs to a PBS cluster from the an
external application. For each job submitted to WSGRAM we request that job
state notifications are sent directly back to our external application.

This has worked well when the notifications are sent back to the application
unencrypted. However, we attempt to encypt this traffic using SSL(ie send
the notifications to https://domain.com), no notificaitions are recieved at
the external application.

I have checked the following

   - There is no log entry indicating a error or warning that there has been
   a problem(debug is turned on)
   - A PersistentSubscription object file is created for the job in the
   Persisted directory
   - I have sniffed the network traffic and I do see 2 tcp connections
   between the WSGRAM server and the external application.

My assumption is that the sending of the job state notification is failing
because of an SSL related warning (ie SSL cert error such as "Do not trust
the CA " or "host name mis-match"). Thus my questions are

   1. Is my assumption above correct
   2. If so, is there a way I can turn off the behavior where the connection
   will fail on a warning?
   3. Also, for the job state notification connection, where is the
   TRUSTED_CA directory, is it in the standard location of either
   ~.globus/certificates or /etc/grid-security/certificates?


Thank you in advance for the assistance with this,


Brian Connolly

Reply via email to