Threatrix Documentation
Threatrix
  • Getting Started
  • Developer Quick Start
  • SecureShip
    • Artifactory Scanning
    • ThreatAgent Scanning
  • Threat Center
    • Creating Account
      • OAuth Login
    • Entity Dashboard
    • User Profile
  • AICertify
    • Reviewing Results
  • codecertify
    • Quick Start
    • Project Summary Tab
    • Components Tab
      • Custom Components
        • Adding
        • Editing
        • Important Notes
      • Header Panel
      • Module Tree Panel
      • Results Panel
        • Card View
        • Risk Graph View
      • Audit History
    • Assets Tab
      • Custom Asset Matches
        • Adding Asset Match
  • securecore
    • Project Dashboard
    • ThreatScan
    • Scan Results
  • Threat Agent
    • Threat Agent Overview
    • Threat Agent - Installation & Scanning
    • Scan Summary Reports
    • Resolving Errors
    • Scanning Container Images
  • Integrations
    • Dependency Managers
      • RENV
    • Build Integrations
      • AWS CodeBuild
      • Azure DevOps
      • Bitbucket Pipeline
      • CircleCI
      • GitHub Action
      • GitLab Pipeline
      • Jenkins Pipeline
    • SCM Integrations
      • GitLab
      • Bitbucket
    • Issue Management
      • Jira
    • Notifications
  • Policy Management
    • Policy Overview
    • Creating Policies
    • Policy Conditions
    • Policy Actions
    • Policy Scopes
  • Administration
    • User Management
    • Organization Settings
      • Organization Knowledge Base
      • Integration
        • Slack Integration
        • Jira Integration
        • Service Keys
    • RBAC
    • Entity Management
    • Okta
      • Okta Org2Org Integration
  • GraphQL API
    • API Overview
  • Resources
    • Dependency Managers
      • PIP
    • Dictionary
    • Licenses
    • Security & Privacy
    • Binary File Support
  • Hybrid / On Premise
    • Getting Started
    • Installation
    • Upgrade
    • Setup
    • Cloud Data Disclosure
    • Troubleshooting
Powered by GitBook
On this page
  • Overview
  • Step 1: Create an Org2Org app
  • Step 2: Threatrix IdP Setup
  • Step 3: Complete org2org Setup

Was this helpful?

  1. Administration
  2. Okta

Okta Org2Org Integration

These instructions wil guide you through the process of creating an Okta org2org integration with Threatrix.

PreviousOktaNextAPI Overview

Last updated 1 year ago

Was this helpful?

Overview

This integration enables members of your team to seamlessly authenticate into the Threatrix app with granted permissions.

This integration requires a 3-step process

  • : The customer configures Threatrix org2org integration in their Okta account

  • : Necessary credentials are provided to Threatrix to complete customer integration with Okta.

  • : The customer completes org2org integration configuration

The total setup and configuration time is approximately 20 minutes.

Step 1: Create an Org2Org app

Login to your Okta administration console and navigate to Applications->Applicatons. Click Brows App Catalog

Select or search "org2org"

Click "Add Integration"

On the next page select SAML 2.0

Scroll down and click “Setup Instructions”

On the page which just has opened navigate to step 6. Copy and save “IdP Issuer URI”, “IdP Single Sign On URL” and download the certificate.

Step 2: Threatrix IdP Setup

Provide the above URI, URL, and certificate to the Threatrix team.

Step 3: Complete org2org Setup

Putting actual values for “Hub ACS URL” and “Audience URI” fields. Go to “Threatrix Integration (Org2Org)” app page, Sign On tab and click Edit.

  • Scroll down to “Advanced Sign-on Settings” section and input data.

  • Into "Hub ACS URL" field input value of "Assertion Consumer Service URL" field provided by the Threatrix team.

  • Into "Audience URI" field input value of "Audience URI" field provided by the Threatrix team.

  • Click Save.

Setup provisioning

Enable API integration, input API token provided by the Threatrix team, click “Test API Credentials” to make sure the token is ok, and click Save.

After adding the token you’ll see the Provisioning tab with the “To App” section selected, click Edit.

Make selections like those shown in the screenshot below and click Save.

Create Treatrix-related groups. Groups are required to identify the organization to which users belong and the user roles.

Go to the Directory/Groups page and create group with the prefix "TRX_ORG_" which will determine organization and groups with the prefix "TRX_ROLE_" which will define user roles.

Then go to the Directory/People page and add groups to desired user(s).

Add the Push Groups Rule

Go back to the Threatrix integration (Org2Org) page, Push Groups tab and add the rule.

Name it "Push Threatrix Related Groups", add filter by prefix "TRX_" and click Save.

Now assign the Threatrix Integration (Org2Org) app to people as shown in the next several screenshots

That’s it! You've completed the setup of Threatrix SAML/Okta org2org Integration.

Give the integration a name. “Threatrix Integration (Org2Org)” for example. Input into Base URL field. Leave other fields default and proceed.

Back to Org2Org setup page, scroll down and paste into “Hub ACS URL” and “Audience URI” fields and click Done.

https://dev-41321907.okta.com
https://dev-41321907.okta.com
Create org2org app
Threatrix IdP setup
Complete Setup