Skip to main content
All CollectionsSecurity
Okta OpenID Connect (OIDC)

Okta OpenID Connect (OIDC)

Instructions for integrating RePro with OKTA OIDC

Updated over 2 weeks ago

Okta OIDC is available for integration with RePro Stream. To get started woth Okta OIDC please follow the OKTA documentation. You will need to sign up for an OKTA Developer account.

Creating Your OIDC Apps at Okta

If you already have your apps set up you can skip to 'xxxx' below.

You will first need to set up your app at the Okta Developer portal. If you have a mobile native app you will also need to create a second Okta app.

  1. Select Applications and then on the sub item Applications page click the Create App Integration.
    ​

  2. Create your web app.

    1. Sign-in method: Select OIDC - OpenID Connect.

    2. Applicaiton type: Web Application.

    3. Fill out the form to set up the Okta app as required.

      Creating your OKTA app.

  3. Create your mobile native app.

    1. As step 2 above but select Native Application after selecting OIDC.

    2. Fill out the form to set up the Okta app as required.

  4. Creating an API Authorisation Server (if you have not created one yet).

    1. At your Okta Portal click Security in the left menu and then API.

    2. Click Add Authorisation Server.

      Creating an API Authorisattion Server
    3. Fill out the form as required.

      Add Authorisation Server form.

Integrating your Okta OIDC apps at RePro Stream.

  1. Head to your Organisation Settings page (if you have a self host server with your own domain head to the equivalent page for your installment) and enable Okta SSO.

    Enabling Okta SSO at RePro Organisation settings page.


    ​

  2. Fill out the Okta OIDC configuration form.

    Fill out the Okta OIDC configuration form.
  1. Okta Domain is found as the base URL of your Okta dashboard in the address bar and looks something like: dev-123456.okta.com - or it could be a custom domain depending on your Okta developer account setup.

  2. API Token is found when you set up an API Authorisation Server as shown in the steps above. You will only be given this key when you create your authorisation server so keep it safe and secure.

  3. API Authorisation Server Audience is found in your authorisation server configuration under Audience e.g. api://default.

  4. API Authorisation Server Issuer is found in your authorisation server configuration under Issuer URI.

  5. Applicaton Client ID is found in more than one place - you can find it under the app title in the list of your Okta apps on the main Applications page or once you have selected your application in the Applications page of your Okta portal.

    Client ID found in Okta Applications page list.
    Finding the Client ID in your Okta App details page.
  6. Native (Mobile) Application Client ID is optional and only required if you have created an Native app at OKTAfor OIDC.

    1. Select your OIDC Native App in the Okta Portal.

    2. Copy the Client ID

  7. Native (Mobile) Redirect URI is optional and only required if you have created an Native app at OKTA for OIDC. This is as you set up the app and requires your mobile app URI.

    1. Select your Okta Native mobile app.

    2. On the details page, on the general settings tab - scroll down to the Login section and find the Sign-in redirect URIs where you find the app URI value e.g. myapp://callback - this is the URI to open your iOS app e.g. myapp:// plus callback to make myapp://callback

Save your settings

Once you have filled out the Okta OIDC form in Repro with the above configuration click SET UP in the bottom right corner.

Updating your settings at RePro:

Enable/Disable Okta SSO and settings (cog) button.

You can update your Okta OIDC settings any time it is enabled by clicking the cog icon to the right of enable toggle for Okta SSO. Once you have updated you can click the UPDATE button in the bottom right of the form. You can disable the Okta integration any time by toggling the Okta SSO toggle off (your current settings will be saved for when you next toggle it back on).

Did this answer your question?