Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

OneLogin SSO (App Catalog)

How to add DevArmor from the OneLogin App Catalog

DevArmor has a dedicated connector in OneLogin's App Catalog, so adding it doesn't require building a custom OIDC app by hand — OneLogin pre-configures the redirect URI and token settings for you. If your OneLogin admin would rather use the generic OIDC connector instead (for example, if the catalog listing isn't visible in your org yet), see OneLogin SSO (Manual).

Prerequisites

  • A DevArmor organization account. If your company doesn't have one, sign up at https://devarmor.com or contact your DevArmor representative.

  • Administrator access to your OneLogin org.

  • DevArmor enables OneLogin SSO per organization. You'll share your integration details with DevArmor in the steps below; DevArmor activates SSO for your organization, typically within one business day.

Supported features

  • SP-initiated SSO: users start sign-in from the DevArmor application.

Not supported:

  • IdP-initiated SSO (launching DevArmor from the OneLogin portal) — sign-in always starts at app.devarmor.com

  • Just-in-Time (JIT) provisioning — DevArmor provisions users on its side; authenticating via OneLogin doesn't create a DevArmor account by itself. See Adding new users after setup.

  • SCIM provisioning

  • Single Logout (SLO)

There's currently no public API for account management. New users are added within the DevArmor application by your organization's DevArmor admin, or by contacting support@devarmor.com.

Configuration steps (OneLogin administrator)

For general background on adding apps in OneLogin, see OneLogin's own Introduction to App Management guide.

  1. In the OneLogin admin portal, go to Applications → Applications → Add App.

  2. Search for "DevArmor OIDC" and select it, then click Save.

  3. Open the SSO tab and copy the Client ID and Client Secret. The redirect URI and Token Endpoint Authentication Method are pre-configured by the connector — unlike the generic OIDC setup, there's nothing to set manually here.

  4. On the Users tab, assign the users who should have DevArmor access.

  5. Send DevArmor the following (see our guide for a secure transfer for the client secret):

    • Your OneLogin domain (for example, yourcompany.onelogin.com, or your custom domain if you use one)

    • The Client ID and Client Secret from step 3

    • The email domain(s) your users sign in with (for example, yourcompany.com)

  6. DevArmor enables SSO routing for your organization and confirms by email.

SP-initiated SSO (end users)

  1. From your browser, navigate to the DevArmor sign-in page at https://app.devarmor.com/sign-in.

  2. Click Sign in with OneLogin and enter your work email address.

  3. You're redirected to your OneLogin organization to authenticate with your OneLogin credentials.

  4. After successful authentication, you're redirected to the DevArmor dashboard.

Adding new users after setup

The same two-step process applies whether DevArmor was added via the catalog or the generic OIDC connector — see Adding new users after setup on the manual setup page (just substitute DevArmor OIDC for the app name in that guide's OneLogin-side step, matching whatever you named it in step 2 above).

Support

PreviousOkta SSO (Manual)
NextOneLogin SSO (Manual)

Last updated

Was this helpful?