Two local certification authorities (CAs) are deployed to test the Globus install and to perform some initial testing. These CAs are:
davidg
and meet
). This CA has the
DN:
O=Vlab, OU=NIKHEF, CN=nikCA Certificate Authority/
Email=davidg@nikhef.nl
This CA also signed the host certificate for a test-bed secure web server (the cert is for *.nikhef.nl). There is some tooling available to convert user certs signed by the CA to PKCS#12 type user certs for use by Netscape and MSIE.
C=NL, O=NIKHEF, CN=NIKHEF CA Organization
Since these `local' CAs will probably not inspire a lot of trust outside NIKHEF, it might be useful to apply for certification with another (new) CA, e.g., a local CA for the WCW, a new CA to be operated by SURFNET (related to the PKI project) or maybe even a commercial CA like Verisign or Twarthe.
But since you can allow for multiple CAs to sign user certs, this is not an immediate issue (as long as all participants trust each other). Note that a specific user cert can be signed by one and only one CA. User key ring support is not currently part of the Globus toolkit (but is is foreseen for some later release).
The following files contain localized information on subject
and CA names:
etc/globus-gatekeeper.cert |
name in this cert (and matching key) is extracted at gatekeeper startup and used to re-write the jobmanager configuration file. |
share/certificates/ca-sign ... |
determined which CA can sign which certificates. |
~/.globus/ ... |
user information. The grid-cert-request
script takes the user cert DN from the cofiguration
script at etc/grid-security.conf . |
etc/grid-security.conf |
Contains the baseDN used for both gatekeeper and user DNs. |
The name of the gatekeeper certificate is generated by the
grid-cert-request
program, using the hostname obtained from the
master etc/gatekeepers.conf
file. Its invication, as taken from