Skip to main content

Set up Single Sign-On (SSO) with Okta

Connect your Okta organization to Patrowl so your team can sign in with their Okta credentials.

Written by Helyette Mehouelley

Overview

Patrowl supports Single Sign-On through OpenID Connect (OIDC). Once SSO is enabled, your users sign in to Patrowl with their Okta account and you manage access centrally from Okta.

Setup takes about 15 minutes and has four steps:

  1. Create an OIDC application in Okta.

  2. Copy your Client ID and Client Secret.

  3. Copy your Metadata URI.

  4. Send these values to Patrowl securely.

Patrowl then completes the configuration on its side.


Before you start

Make sure you have:

  • Administrator access to your Okta Admin Console.

  • The Sign-in redirect URI provided by Patrowl. If you don't have it yet, ask your Patrowl Customer Success Manager.

💡 Tip: keep a text editor open while you follow this guide. You'll copy three values along the way and send them to Patrowl at the end.

Step 1: Create a new application in Okta

  1. In the Okta Admin Console, go to Applications > Applications.

  2. Click Create App Integration.

  3. For Sign-in method, select OIDC - OpenID Connect.

  4. For Application type, select Web Application.

  5. Click Next.

  6. In App integration name, enter a name your users will recognize, for example Patrowl.

  7. In Sign-in redirect URIs, paste the Sign-in redirect URI provided by Patrowl.

  8. In Sign-out redirect URIs, paste the same URI and add /logout_response to the end.

  9. Click Save.

Example of redirect URIs

  • Sign-in redirect URI: https://<your-patrowl-url>/endpoint

  • Sign-out redirect URI: https://<your-patrowl-url>/endpoint/logout_response

⚠️ Important: the Sign-out redirect URI must match the Sign-in redirect URI exactly, with /logout_response added to the end. Check for typos, extra spaces, and trailing slashes.

Step 2: Copy the Client ID and Client Secret

After you save, Okta opens your new application on the General tab.

  1. Scroll down to the Client Credentials section.

  2. Copy the Client ID.

  3. Copy the Client Secret.

Patrowl needs both values to configure OIDC.

🔒 Security: the Client Secret works like a password. Never share it in plain text, in a support chat, or in an unencrypted email.

Step 3: Copy the Metadata URI

  1. In the Admin Console, go to Security > API.

  2. Open the Authorization Servers tab and select your authorization server (usually default).

  3. On the Settings tab, copy the Metadata URI.

Patrowl needs this value to configure OIDC.

Step 4: Send the information to Patrowl securely

You now have the three values Patrowl needs:

  • Client ID

  • Client Secret

  • Metadata URI

To send them securely:

  1. Create a .txt file that contains the three values.

  2. Compress the file into a password-protected ZIP archive.

  3. Email the ZIP file to your Patrowl Customer Success Manager.

  4. Send the ZIP password by SMS.

🔒 Why two channels? Sending the file and the password separately means that if one channel is compromised, your credentials stay protected.


What happens next

When Patrowl receives your information, the team configures SSO on your account and lets you know when it's active. Your users can then sign in to Patrowl with their Okta credentials.

We recommend testing the sign-in with one user before rolling it out to the whole team.


Troubleshooting

A user gets an error when signing in through Okta

Check that the user is assigned to the Patrowl application in Okta, under Applications > Patrowl > Assignments. Users who aren't assigned to the app can't sign in.

I get a "redirect URI mismatch" error

The redirect URIs in Okta don't exactly match the ones provided by Patrowl. Compare them character by character, especially the /logout_response suffix and trailing slashes.

I can't find the Metadata URI

You need administrator access to the Security > API menu. If you don't see it, ask your Okta administrator.

I regenerated the Client Secret in Okta

The previous secret stops working right away. Send the new secret to Patrowl using the secure method in Step 4.


Need help?

If you have a question about this setup, contact your Patrowl Customer Success Manager or start a conversation with us from the chat.

Did this answer your question?