As consortium access is currently limited to INTL5 Persons (Australia, Canada, New Zealand, U.K. and U.S.) each participant will need to complete the following process to gain access to the FACE® Consortium member collaboration site ("Plato"), attend meetings, and participate in the consortium.
- Step 1 will invoke your membership access to the FACE Consortium
- Step 2 will create your user id for The Open Group
- Step 3 will grant access to the FACE Consortium Collaboration Site (Plato)
- Step 4 will grant access to the FACE Consortium member’s GitLab
- Step 5 will setup Two Factor Authentication (2FA)
Step 1 – Submit INTL5 Person Attestation Form: Have the appropriate person in your organization fill out, sign, and submit the Attestation Form per the instructions on the form. The form can be downloaded HERE.
Step 2 – Register for an Account: Please go here and set up a username and password by registering in our system.
Once you have completed and submitted the form, you must be sure to complete the email verification process to complete your registration. The email verification will be completed via a confirmation sent to your email inbox. The request for email verification will come from no-reply@opengroup.org. Follow the instructions to verify your email. If you have an issue with the email verification or account creation, please contact us at systems-support@opengroup.org.
Step 3 - After the above steps are completed, we will provide the details on how to access the Member Only Collaboration Site (Plato), along with instructions on how to self-subscribe to any subcommittees in which you wish to participate.
*Optional Steps if you want GitLab member access (you can finish these later if you deem to need GitLab access:
Step 4 – Self-Registration for GitLab Access: To gain access to the Consortia GitLab content for FACE, first log into the Collaboration Site (Plato). On the left navigation bar, please click on the “Join Site GitLab Group (8)”. This will create an account for you on Consortia GitLab, and grant access to the FACE top level group. After joining, the button will change to “Access Site GitLab Group (8)”, which can be used to access the content. Direct Links to GitLab content will also work, once you have joined the group – you do not need to go through the Collaboration Site every time.
The Consortia GitLab server uses the same Single Sign-On (SSO) server that the Collaboration Site does, so the username/password will be the same for both. In addition, if you’ve already signed into one of the servers, the other will allow access without prompting for a password.
Note For Existing Accounts: Accounts established prior to August 1, 2024 were created manually rather than using the Collaboration Site. When these users use the “Join Site GitLab Group” button, the Collaboration Site will attempt to associate the existing account. This is done by looking up the user first by SSO username (if they have directly signed into GitLab using the SSO), then by email address. It is possible that email addresses in GitLab are out of sync with the Collaboration Site, which can lead to errors in creating / associating accounts. This usually appears as an error saying that the user already exists or is already in the Group. In some unusual cases, it results in a duplicate account. If any of these happen to you, email ogface-admin@consortia.opengroup.org for help resolving.
Note for CTS Developers: The Conformance Test Suite is managed on a different GitLab server, and membership is assigned manually. Email ogface-admin@consortia.opengroup.org to request access.
Step 5 – Set up 2FA for GitLab: On first login to the Consortia GitLab, you will be prompted to set up a Time-based One Time Password (TOTP) Two Factor Authentication (2FA). This helps secure your account against impersonation attacks. For more details on setting this up, see the Knowledge Article titled How do I set up Two-Factor Authentication in GitLab.