|
|
| (2 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | [[Category:Grid computing]] | + | #REDIRECT[[Swestore Documentation Moved]] |
| − | [[Category:SweGrid user guide]]
| |
| − | [[Category:SweStore]]
| |
| − | [[Category:SweStore user guide]]
| |
| − | | |
| − | [[Getting started with SweGrid|< Getting started with SweGrid]]
| |
| − | | |
| − | [[SweStore|< SweStore]]
| |
| − | | |
| − | Most of the standalone third party tools installed on SNIC resources and your own machine will not be able to use a <tt>.p12</tt> certificate bundle (or <tt>.pfx</tt> if you exported from IE), as that format is intended primarily for secure transport and backup of certificates and their private keys.
| |
| − | | |
| − | Instead of a single <tt>.p12</tt> file, they expect a pair of files in <tt>.pem</tt> format, one containing the certificate and the other containing the private key that matches the certificate.
| |
| − | | |
| − | == Uploading and conversion of the .p12 for your target machine ==
| |
| − | | |
| − | As the authentication methods for clusters differ, this section will defer to documentations for your particular site when it comes to transferring files to and from the cluster storage.
| |
| − | | |
| − | The goal is to end up with a <tt>.globus</tt> directory in your home directory, containing two files named <tt>usercert.pem</tt> and <tt>userkey.pem</tt>.
| |
| − | | |
| − | The instructions below assume that your exported certificate file is named <tt>export.p12</tt> directly in your home directory. If it's a <tt>.pfx</tt> or with a different name, change <tt>export.p12</tt> in the instructions to your actual filename or rename your file to <tt>export.p12</tt>.
| |
| − | | |
| − | * Transfer the <tt>export.p12</tt> file to your home directory on the cluster.
| |
| − | * Get an interactive shell on the login node, via ssh.
| |
| − | * If an .globus directory already exists, rename it with something like
| |
| − | <tt>mv ~/.globus ~/.globus-old</tt>
| |
| − | * Create the directory with
| |
| − | <tt>mkdir ~/.globus</tt>
| |
| − | <tt>chmod 0700 ~/.globus</tt>
| |
| − | * Extract and protect the private key part of <tt>export.p12</tt>:
| |
| − | openssl pkcs12 -nocerts -in ~/export.p12 -out ~/.globus/userkey.pem
| |
| − | * When asked for import password, specify the password specified when exporting the certificate bundle from your browser. The PEM pass phrase should be a new password that you need to provide whenever using the certificate for tasks like generating a proxy certificate. The output from this command will be similar to the following:
| |
| − | Enter Import Password: *******
| |
| − | MAC verified OK
| |
| − | Enter PEM pass phrase: *******
| |
| − | Verifying - Enter PEM pass phrase: *******
| |
| − | | |
| − | * Extract the public client certificate part of <tt>export.p12</tt>:
| |
| − | openssl pkcs12 -clcerts -nokeys -in ~/export.p12 -out ~/.globus/usercert.pem
| |
| − | * The output will be similar to the following:
| |
| − | Enter Import Password: *******
| |
| − | MAC verified OK
| |
| − | * Finally ensure that only your user is allowed to read the private key file. This is important, both for security and due to some tools refusing to use private keys with insufficient restrictions.
| |
| − | chmod 0400 ~/.globus/userkey.pem
| |
