Project

General

Profile

Bug #15674

Bad CA message in frontend

Added by Marco Mambelli almost 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Category:
-
Target version:
Start date:
02/27/2017
Due date:
% Done:

0%

Estimated time:
First Occurred:
Occurs In:
Stakeholders:
Duration:

Description

Hi Marco,

We had issues with Glideinwms frontend at UNL and the problem was traced back to wrong info in the docs. See below for comments from Derek. Can you please do some sanity checks and update the docs?

— — From Derek
Brian figured out the problem. You should update the document https://twiki.grid.iu.edu/bin/view/Documentation/Release3/InstallGlideinWMSFrontend#Example_of_automatic_proxy_renew
take out the "-old" option to grid-proxy-init
So it uses the host cert, to create an old non-rfc proxy.
then the script creates a new proxy from that proxy, but it is RFC.
so… when globus tries to parse the proxy, it goes up the certificate chain. When it sees the non-rfc proxy, it thinks it's an CA, which is not installed on the system.
hence the bad CA.
_____________________________________
Parag Mhashilkar

History

#1 Updated by Marco Mambelli almost 4 years ago

  • Status changed from New to Closed
  • Target version set to v3_2_18

Also available in: Atom PDF