Embedded Files
This section explains the setup of the OAuth 2.0 authentication for Relatics administrators
This section explains the setup of the OAuth 2.0 authentication for Relatics administrators
Relatics updated their webservice security with the OAuth 2.0 authentication protocol. All applications using webservices to exchange data with Relatics need to support this authentication protocol to be able to access the data stored in Relatics.
In the Edit Environment dialog in the Neanex Connector the user needs to specify a ClientID and Secret key to get access to the Relatics environment. This ClientID and Secret key is specified in the Relatics environment studio. Below you will find a detailed description how to set and access this information.
Navigate to the environment studio on your Relatics environment and click on Clients in the App Authorization section.
Right click in the table header and press Create to add a new Client. Define a name for the new Client, for example "Neanex Connectors".
Double click in the Client Secret row to set the secret key. Copy the key and store it somewhere before you press SET. The key will only be visible once! When you lost the key you need to set it again.
Right click in the Allowed redirect URIs table and press Create to add a new URI. The URI consists of your environment URL with the addition of /oauth2/retrievecode
For example: https://neanex.relaticsonline.com/oauth2/retrievecode
The Relatics administrator needs to provide the ClientID and Secret key to all the Neanex Connector users to be able to access the Relatics environment.
The first time you log in from the Neanex Connector, you need to grant access to the Neanex Connector to allow the application to use your account to access the Relatics API and Relatics Webservices.
At your next login attempt you will get access to the Relatics environment immediately after logging in with your Relatics username and password.
Parent topic: Setup
Report abuse