Set up for:
The BCP IDE supports OAuth 2 and in Nexar the Authorization Code
, Client Credentials
and (when enabled) Resource Owner Password
flows are configured for accessing the API.
Begin with the “Connection Settings” dialog box (click on the gear icon at the upper right of the page) and under the "Authorization" tab select “OAuth2” from the drop-down:
The configuration details will be slightly different for applications that only use the supply queries (Nexar queries that are prefixed with "sup") and applications using the design queries to access A365 design data (prefixed with "des").
Supply Applications
Supply applications use a Client Credentials
flow with the following settings:
Type: OAuth 2
Grant Type: Client Credentials
Access Token URL: https://identity.nexar.com/connect/token
Client ID: << from the application details page >>
Client Secret: << from the application details page >>
Scope: supply.domain
Once you have entered all the details, click the “Fetch Token” button to get the token and click the “Apply” button to close the settings dialog.
Design Applications
Design applications use an Authorization Code
flow. Configure the properties as below:
Authorization URL: https://identity.nexar.com/connect/authorize
Access Token URL: https://identity.nexar.com/connect/token
Client ID: << from the application details page >>
Client Secret: << from the application details page >>
Redirect URL: https://api.nexar.com/graphql
Scope: openid profile email user.access design.domain offline_access
NB: Don't forget to set the Redirect URL and Scope fields (not shown) accurately!
Remember the "Show Details" button for the application will get you access to the following details and allow you to configure the callback URL - don’t forget to do that!
Once you have entered all the details, click the “Fetch Token” button to get the token and click the “Apply” button to close the settings dialog.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article