Belle II Registration FAQ
My question is not in here?
If you want us to add another tip here, let us know via b2-registration-support_AT_belle2.org .
My browser complains about connection / SSL problems?
Connection errors such as 'SSL_ERROR_HANDSHAKE_FAILURE_ALERT' are due to old or missing CA certificates in your browser. You might want to check Preferences / Advanced / Certificates / View Certificates / Servers and Authorities . Also consider to use another browser. We have good experiences with firefox and we saw also safari on MACs working. From our experience there is usually someone in your group or institute who managed.
What is my Belle II account art DESY good for?
The credentials (account + passwd) you got through the registration procedure can be used to access the new Belle II web pages and the new Wiki.
Do I have to renew my Belle II account at DESY yearly as at KEK?
No, this is not necessary.
What about a paper-based registration?
A Belle II Paper-based Registration procedure is possible but not recommended.The two main steps of authentication ('Who are you?') and authorization ('Are you in Belle II?') have to be carried out manually. Therefore it requires more work from your side and from the administrators in your and our institute. Hence we would like to strongly encourage you again to go for the Grid user certificate based registration since you will need this certificate later on for accessing data and submitting jobs in the Belle II Grid anyways.
Do I have a DESY account?
If you were able to or are still able to login to 'bastion.desy.de' , you got a DESY account earlier which can be used for Belle II. Contact b2-registration-support_AT_belle2.org . A new registration attempt via the portal would fail.
I have already a Grid user certifcate?
Belle II collaborators who have a already a Grid user certificate and are already member of the VO 'belle' can go directly to the registration portal. Make sure the Grid user certificate is in the browser!
I have a already a DESY account?
Belle II collaborators who have already a DESY account should contact b2-registration-support_AT_belle2.org . The account can be used for Belle II. A Grid user certificate and the membership in the VO 'belle' is strongly recommended though.
Is my Grid user certificate in the browser?
Check existence and validity of your Grid user certificate in your firefox browser in Preferences / Advanced / Certificates / View Certificates / Your Certificate.
I want to change my password?
Login to 'bastion.desy.de' and use the command 'passwd'. It connects to the DESY registry which manages the access to afs, web pages, and ATLASSIAN tools (confluence, stash, agira, bamboo). The Sympa ML server and Indico are not managed automatically.
I changed my DESY password using 'passwd' on a DESY login host?
The command 'passwd' issued on a DESY login host, e.g. 'bastion.desy.de', connects to the DESY registry which manages the access to afs, web pages, and ATLASSIAN tools (confluence, stash, agira, bamboo). The Sympa ML server and Indico are not managed automatically.
I lost my password?
If your password got lost, please contact b2-registration-support_AT_belle2.org .
I lost the password of my Grid user certificate?
As the private key the password is as the the word implies 'private'. It is only known to you. Unfortunately you must request a new certificate.
How to test my Grid user certificate in ~/.globus ?
Grid users usually have exported their Grid user certificate to ~/.globus to use it with Grid commands such as 'voms-proxy-init', 'dirac-proxy-init', or 'gb2_proxy_init'. The follwing commands may help to investigate the situation.
The directory:
> cd ~/.globus
> ls -l
-r--r--r-- 1 usercert.pem
-r-------- 1 userkey.pem
Checking if public (cert) and private (key) match:
> openssl x509 -noout -modulus -in usercert.pem | openssl md5
> openssl rsa -noout -modulus -in userkey.pem | openssl md5
Checking subject, issuer, and validity dates:
> openssl x509 -subject -issuer -email -dates -noout -in ~/.globus/usercert.pem
Recreating a single file with public and private key to be improted into a broser:
> openssl pkcs12 -export -out my_cert.p12 -inkey userkey.pem -in usercert.pem