Register a VO

Registering a VO means allowing users of a specific Virtual Organization to use DiracX services. In practice, this can be done once an external IdP is used for managing such VO. By default all VOs managed by a DIRAC/DiracX instance are already "registered" (or "enabled", in other words). There is anyway the possibility to "Disable" VOs by filling the option DiracX > DisabledVOs with the list of VOs that can not use DiracX:

??? example "Configuration example"

    ```yaml
    DiracX
    {
      DisabledVOs = vo_x, vo_y
    }
    ```

Prerequisites

You have access to your DiracX instance URL.
It is better to have admin rights on the VO’s IdP instance (e.g. Indigo IAM).

Manage Users

Generate an OIDC client

Log in to your VO’s IdP instance.
Create a new OIDC client with:
- Client secret: none
- Redirect URIs:
```
https://<your‑diracx‑url>/api/auth/authorize/complete
https://<your‑diracx‑url>/api/auth/device/complete
```
- Grant type: authorization_code
- Scope: at minimum openid, profile and email

Configure DiracX

In your DIRAC CS, add under DiracX > CsSync > VOs > <VO> > IdP:

Configuration example

DiracX
{
  CsSync
  {
    VOs
    {
      <VO>
      {
        IdP
        {
          ClientID = "<OIDC‑client‑ID>"
          URL = "https://<your‑idp‑instance>/"
        }
      }
    }
  }
}

To add specific users, list their subject‑IDs under UserSubjects:
Configuration example
```
DiracX
{
  CsSync
  {
    VOs
    {
      <VO>
      {
        UserSubjects
        {
          <username from dirac> = <user id from the IdP instance>
          ...
        }
      }
    }
  }
}
```
Note

User IDs are associated to the usernames that are defined in the Registry > Users section. This allows DiracX to retrieve the groups they belong to and their properties.

Automatic population of the UserSubjects

The DIRAC VOMS2CSAgent can populate this list for you from an IAM server. For that you need to enable the UseIAM flag to True.

After saving, you should sync the configuration with DiracX. Dirac Groups and properties should then be associated to users defined in the DiracX section. See the previous step Convert CS for a refresher.
Remove the VO from the DiracX > DisabledVOs list

Interact with Computing Elements

Client configuration is still managed through the DIRAC configuration so far. See Submitting pilots to CEs using tokens for further details.

Interact with Storage Elements

This isn't possible yet as the interaction hasn't yet been finalized by WLCG. See the roadmap for details.