Overview
To connect with ADOXX (Client Credentials), you need:- Base URL – The address of your ADOXX instance, including the product/version path segment (e.g.
yourserver.com:8000/ADOXX). - Client ID – The Client ID of an OAuth 2.0 client registered for the Client Credentials Flow.
- Client Secret – The Client Secret generated for that client.
If your ADOXX instance is BOC’s cloud-hosted (SaaS) offering rather than self-hosted, some settings may be pre-configured or restricted rather than self-service — for example, SaaS customers configure their CORS policy by contacting
hotline@boc-group.com instead of editing it directly. If you can’t find or access the screens in the steps below, contact BOC support to confirm what’s self-service on your plan.Prerequisites
- Administrative access to the ADOXX Administration.
Instructions
Step 1: Create a technical user
The Client Credentials Flow runs requests in the context of a technical user, so create one first.- Go to the Users page and click New User.
- On the General tab, enter a name (e.g.
Technical_StandardRESTfulServices) and set a password. - On the Groups and roles tab, assign the user to the Default user group.
- On the Repository tab, assign only the repository holding the data you want to query.
- Click Create.
- Hover over the new user, click More > Edit, and on the General tab enable Trusted login.
Step 2: Set the Base URL and link the technical user
- Go to Settings > System settings > System.
- In the Base URL field, enter the URL where the instance can be reached from other machines, e.g.
http://<SERVER_NAME>:<TOMCAT_PORT>/ADONIS16_0/(default port is8000). - Nango’s Base URL field expects a different format: no protocol and no trailing slash — Nango always connects over
https://. Strip both from the value above before entering it in Nango, e.g.<SERVER_NAME>:<TOMCAT_PORT>/ADONIS16_0. - Click Select users and choose the technical user created in step 1.
- Click Save.
Step 3: Enable the REST API and OAuth 2.0, and define a scope
- Go to Settings > Standard RESTful Services > General.
- Enable Enable Standard RESTful Services globally.
- Switch to the OAuth 2.0 tab and enable Enable OAuth 2.0.
- Enable the REST scenarios (Repository / Users / Metamodel) your integration needs — a disabled scenario returns
403 FORBIDDENfor its endpoints. - Under Scopes, click Add scopes and create at least one scope: give it a name (e.g.
REST_READ), optionally restrict it by IP, and select the technical user from step 1. - Save your changes.
Step 4: Register an OAuth 2.0 client
- Go to Home > More options > OAuth 2.0.
- Select OAuth 2.0 enabled.
- Click Add to create a new client.
- Fill in the Client Data form:
- Type:
Confidential(able to securely store a client secret). - ID: a unique client identifier, kept simple (avoid special characters).
- Name: a display name for the client application.
- Redirect URI: the form requires this field even though it’s unused for the Client Credentials Flow — any placeholder value works.
- Secret: click Generate to create the Client Secret.
- Type:
- Click Save changes. Copy the ID and Secret — these are your Client ID and Client Secret.
Step 5: Enter credentials in Nango
- Open the Nango Connect form.
- Enter your Base URL (from step 2), Client ID, and Client Secret (from step 4).
- Submit the form, and you should be successfully authenticated.
