Skip to content

10.1.2.3 Robot Certificate

A Robot certificate represents an experiment service, pilot or automated task — not a human.Every Robot certificate must have a clear responsible person; the system writes the current SSO user's LDAP email into the SAN and the system metadata. The procedure is identical to a user certificate (see10.1.2.1) except for what you fill in on theEdit Subjectpage:

Robot certificate: enter Experiment and Submodule / purpose

  • Experiment: the experiment name, e.g.JUNO. Only letters, digits, dots, underscores and hyphens.
  • Submodule / purpose: the submodule or purpose, e.g.pilot. Letters, digits, spaces, dots, underscores and hyphens.
  • Organization Unit / Organization: choose the actual responsible unit and organization from the dropdowns.
  • The second CN is fixed toRobotautomatically; do not, and cannot, enter a user short account.

Check the DN in the summary. WithJUNOandpilot, the expected result is:

CN=JUNO pilot,CN=Robot,OU=,O=,O=HEP,C=CN

The remaining steps (private key password, submission, RA review, export password at download time) are exactly the same as for a user certificate.

The SAN of a Robot certificate contains only the responsible person's email andno DNS names: do not deploy it as a Host certificate on a web service, and do not share it with people outside that experiment or service. When the responsible person or the purpose changes, or the key is compromised, request revocation and re-apply.

FAQ

SeeFAQ.

AI 助手
快速提问 ×

有问题?输入后跳转到对话页继续交流

Baidu
map