Create an OAuth Client

An OAuth client must be created in the Lobby to use Aconex and Lobby APIs.

To create an OAuth client:

1. Select  Navigation Menu and select OAuth Clients.
2. Select  Add.
3. On the Add OAuth Client panel, complete the following fields:
   1. Name: Enter a unique and meaningful name for the integration.

      If you think you will only ever have one integration, you can simply use your organization name like "Majestic Inc.".

      If you intend to build multiple integrations, consider a name that describes the purpose of the integration like "Majestic Inc. Package Builder".

   2. Description: Enter a meaningful description for the integration, such as "Connects Majestic's Package Builder with Aconex".
   3. Resource Application: Select Aconex or Lobby as the resource application.
   4. Type: Select the type of integration. Options are Web Server Application, Installed Application, Non-Interactive Integration, and User-Bound Integration (not available when Lobby is selected as the Resource Application). For additional details, see OAuth Clients.
   5. If you selected Web Server Application or Installed Application, complete the following:
      • Redirect URL: Enter a redirect URL. To add an additional URL, select Add Redirect URL. See Redirect URLs below more more details.
   6. Organizations: Select one or more organizations to which the client will be provisioned. The list displays the organizations for which you are an organization administrator. For User-Bound Integration, this is your home organization. The Organizations field does not display.
   7. If you selected User-Bound Integration, complete the following:
      • User Account: Select a Lobby user account that will be bound to the integration. The Lobby user account will be linked to one or more Aconex user accounts.
   8. If your Resource Application is Aconex, review and acknowledge the Terms of Use section.
   9. Select Add.
   10. If you selected Non-Interactive Integration, contact Oracle Support to provide your public certificate. If you have your own identity domain, you can upload the certificate.

Redirect URLs

You may add a single redirect URL or multiple.

Check with your technical team for what redirect URLs need to be configured for this OAuth client.

If you are creating an Installed Application, RFC 8252 states that should use either a Private-user URI scheme redirect or a Loopback redirect URI, each of which are described below.

A Private-user URI scheme redirect uses a custom URI scheme that has been added on the device for your application, taking the form:

scheme:/pathregister

Here's an example:

com.example.app:/oauth2/callback

A Loopback redirect URI uses the "http" scheme with the loopback IP literal and whatever port the application is listening on, taking the form:

http://127.0.0.1:{port}/{path}

Here's an example:

http://127.0.0.1:54001/oauth2/callback

If your Installed Application loops through a number of ports to find an available port for binding the callback, you may add a single loopback redirect URI with a wildcard (*) port identifier, rather than multiple redirect URIs.