Getting a certificate for the T2: Difference between revisions

From T2B Wiki
Jump to navigation Jump to search
mNo edit summary
No edit summary
 
(34 intermediate revisions by 6 users not shown)
Line 1: Line 1:
If you need grid access on the T2, please follow all the steps below: <br> <br>
If you need grid access on the T2, please follow all the steps below: <br> <br>
[ This page is new. Any comments are welcome ! The old page is [[Certificates_and_VOs|here]] ]


=== First time certificate ===
# [[Obtaining_a_certificate | Get a Grid certificate (new)]].
# If you belong to ULB or VUB: [[Obtaining_a_certificate | Get a certificate (new)]] , to UA or UG: [http://quattor.begrid.be/trac/centralised-begrid-v5/wiki/Access_to_BEgrid Get a certificate (old for now)] . ''If you already have a CERN grid certificate and wish to use this one, you can go to the next step directly.''
#:*NB: for now, this does not work for users from UGent. Get a CERN certificate for that.
# Extract your certificate from your browser: '''[[Chrome]]''' | '''[[Firefox]]'''
#:*If you already have a CERN grid certificate and are associated to a Belgian university, you can temporarily use the CERN certificate. But, for accounting reasons, we need you to get a Belgian certificate.
#:*If you are not from a Belgian institute, request a certificate through your national institute.
# [[certificate_to_UI | Put your certificate on the UIs]]
# [[certificate_to_UI | Put your certificate on the UIs]]
# [[Register_to_the_CMS_VO|Register to the CMS VO]]
# Register to the VO
# [[SiteDB | Check if your certificate is ok on SiteDB]]. Note the DN.
#::'''!!! In case you already have an old certificate registered to the VO, read [[What if your DN has changed?|this page]] on how to deal with it !!!'''
# Send a mail to grid_admin@listserv.iihe.ac.be with your DN in order to have write access on the T2.
#:* '''CMS'''
# [[CERN_certificate_management | Check that your certificate is the only one registered on the CERN website.]]
#:*# [[Register_to_the_CMS_VO|Register to the CMS VO]]
# [[Check_Certificate_UIs | Check if everything works fine on the mX machines]]
#:*# [[SiteDB | Check if your certificate is ok on SiteDB]]. Note the DN.
 
#:*# [[CERN_certificate_management | Check that your certificate is the only one registered on the CERN website.]]
=== Certificate renewal ===
#:* '''IceCube'''
As we switched the company who provides us with certificates, you need to follow the 'First time certificate' to have a new one, this until December 2016 at least.
#:** [[Register_to_the_IceCube_VO|Register to the IceCube VO]]
#:* '''Solid'''
#:** [[Register_to_the_Solid_VO|Register to the Solid VO ]]
#:* '''Others'''
#:** [[Register_to_the_Beapps_VO|Register to the Belgian VO (beapps) ]]
# Send a mail to the T2B support (grid_adminATlistserv.vub.ac.be) with your DN in order to have write access on the T2.
#:* You can find it via the following commands on the cluster, once your certificate has been installed there:
<pre>
voms-proxy-init
voms-proxy-info --identity
</pre>
::Send us the result of the last command
<br>
:5. [[Check_Certificate_UIs | Check if everything works fine on the mX machines]]

Latest revision as of 14:48, 17 January 2022

If you need grid access on the T2, please follow all the steps below:

  1. Get a Grid certificate (new).
    • NB: for now, this does not work for users from UGent. Get a CERN certificate for that.
    • If you already have a CERN grid certificate and are associated to a Belgian university, you can temporarily use the CERN certificate. But, for accounting reasons, we need you to get a Belgian certificate.
    • If you are not from a Belgian institute, request a certificate through your national institute.
  2. Put your certificate on the UIs
  3. Register to the VO
    !!! In case you already have an old certificate registered to the VO, read this page on how to deal with it !!!
  4. Send a mail to the T2B support (grid_adminATlistserv.vub.ac.be) with your DN in order to have write access on the T2.
    • You can find it via the following commands on the cluster, once your certificate has been installed there:
voms-proxy-init
voms-proxy-info --identity
Send us the result of the last command


5. Check if everything works fine on the mX machines