Registration of a Virtual Organisation (VO)¶
In order to request and register a new VO, send an email to our Helpdesk, providing the following information:
- VO name
- VO description
- VO manager
- VO acceptable use policy. Templates can be found here: odt / pdf.
We will get in touch with you, while setting up the VO or if something is missing.
What is this about? Why do I need a VO?
- VO are technical representations of (research) groups and are the key element of authorisation in the Helmholtz Cloud.
- Some services don’t need VOs, but most do, in order to control access granted to users and groups. See also our explanation of the AAI concepts.
- Don’t hesitate to ask us via our Helpdesk, should you have any further questions.
You (as a VO admin) need to be able to authenticate with the assurance of RAF Cappuccino, i.e. you need to identify with your passport at your Identity Provider.
As an administrator of a Virtual Organisation you take a substantial share of responsibilities for a working process. The requirements come from the Services. Many services have requirements on the quality of the user identity assurance and on the general quality of the identity provider.
Depending on the service (in this case those allow shell access or data storage) this often requires the users to have shown a passport at their home-IdP and also require the home-IdP to support certain security procedures.
In Helmholtz AAI we want to enable users for which those criteria often aren’t met. Therefore, we offer the possibility to add all kinds of users to a VO, but we require the VO admin to guarantee that an appropriate level of identity vetting has taken place.
Further information about Policies¶
As defined in the top level policy, VO administrators have several tasks to fulfil:
Abide by the following policies:
If necessary, define AUP and PP policies for your VO by extending the following templates:
In most cases, a PP is not necessary if the VO is managed at unity and you do not additionally process any personal data.