SSO for the Paying Organization

Follow these steps to enable Single Sign-On (SSO) for your organization.

Please read through all steps before you begin this process. Make sure you inform all Aconex users in your organization that the way they sign into Aconex will change. 

You must complete all steps sequentially to ensure your SSO configuration is a success.

  1. Before you begin your technical contact must identify:
  • If your organization uses other Oracle products, such as P6, OPC, Unifier, ERP, etc.
  • If you have users in your organization that will not be included in your SSO system.
  • If your organization uses the AU2 instance of Aconex.

If so, please contact Oracle Support to discuss your requirements. You may need to follow a different process.

  1. All users in your organization must have Lobby accounts. Your Org Admin can use the batch onboarding tool to create Lobby accounts for all your users.
  2. Your technical contact completes the configuration checklist and attaches it to a support request ticket. You may need help from your Oracle Representative.

    Important: If your organization already has a cloud account you must skip this step and proceed to step 6 to configure your Identity Domain. You'll submit the checklist later after you've configured your Identity Domain.
  3. Oracle creates an Oracle Cloud account (if required, as you may already have one). Your technical contact will be notified by email when this is completed.
  4. Your technical contact activates the account. They will receive an email with details on how to do this.
  5. Your technical contact sets up the Identity Domain with the SAML configuration for their Identity Provider (e.g. Entra ID, ADFS, or other). You may need assistance from your organization's IT department.
  6. Your technical contact replies to the support request ticket created when your Identity Domain was created, and provides the ID for the account. The easiest way to do this is to paste your Domain URL into the ticket.
    The URL will look something like this: https://idcs-<ID>.identity.oraclecloud.com/ui/v1/myconsole
    You can find your Domain URL in the overview screen. Learn more

    Note:
    If your organization already had a cloud account at step 3, you can now submit the configuration checklist on a support request ticket and also provide your Domain URL.
  7. Oracle will configure the Lobby to use your Identity Domain. Your technical contact will be notified via the support request ticket when this is completed.

    Important: Your technical contact must complete step 9 as soon as possible after receiving notification from Oracle. Completing this step promptly will minimise disruption to your organization's Aconex access.
  8. Your technical contact creates an Identity Provider Policy in your Identity Domain. You may need assistance from your organization's IT department. 
  9. Your technical contact must test signing in to the Lobby to ensure the SSO authentication is successful. You should be taken to your organization's Single Sign-On screen. Enter your SSO username and password, and the Lobby will open. If this does not happen, you must go back and complete the previous step.
  10. Your organization's users will be redirected to your organization's Single Sign-On screen when they next try to access Aconex or the Lobby. If they are not automatically redirected, they need to click the change email address icon on the sign in screen, re-enter their email address, and click Sign In.