Introduction to OKTA

It is recommended to be familiar with OKTA prior to the setup with Trax.

For more information view https://developer.okta.com/docs/concepts/how-okta-works/

​

Prerequisites 

1. OKTA must be implemented on the client's side

​

Trax Authentication Configuration

1. Create Trax application on OKTA according to the following link: 
   https://developer.okta.com/authentication-guide/implementing-authentication/auth-code
   
   The following data is required to be configured when creating the Trax application in OKTA- for the redirect_uri please insert the following:

   • https://services.traxretail.com/auth/v3/oauth2callback/​

   • https://services-int.trax-cloud.com/auth/v3/oauth2callback/

   • https://services-int.trax-cloud.com/auth/v4/oauth2callback/

   • https://services-int.traxretail.com/auth/v4/oauth2callback/
      

2. Go to API authorization servers tab > add authorization server
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
    

3. Configure the access policies and assigned to the relevel users
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
    

4. Add rule according to internal policy
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
   
    

5. Once the Trax application is created, the following will be provided by the client:

   • Client id

   • Client secret

   • authServerId (e.g. https://domain.okta.com/oauth2/default)

   • list of domains

   • The client will provide a test user that Trax will use to test the connection

   • When all tests are successful, the authentication setup is completed​