Onboarding an App Using Okta Credentials
Table of Contents
Expand all | Collapse all
-
-
- What’s Data Security?
- Navigate To Data Security in Cloud Management Console
- Activate Data Security on the Hub
- Access Data Security for Standalone SaaS Security
-
- Allowed List of IP Addresses
-
- Begin Scanning an Amazon Web Services App
- Begin Scanning a Bitbucket Cloud App
- Begin Scanning a Box App
- Begin Scanning a Cisco Webex Teams App
- Begin Scanning a Citrix ShareFile App
- Begin Scanning a Confluence App
- Begin Scanning a Confluence Data Center App
- Begin Scanning a Dropbox App
- Begin Scanning a GitHub App
- Begin Scanning a GitHub V2 App
- Begin Scanning a Gmail App
- Begin Scanning a Google Cloud Storage App
- Begin Scanning a Google Drive App
- Begin Scanning a Jira Cloud App
- Begin Scanning a Jira Data Center App
- Begin Scanning a Microsoft Azure Storage App
- Begin Scanning a Microsoft Exchange App
- Begin Scanning Microsoft Office 365 Apps
- Begin Scanning a Microsoft Teams App
- Begin Scanning a Salesforce App
- Begin Scanning a ServiceNow App
- Begin Scanning a Slack for Enterprise Grid App
- Begin Scanning a Slack Enterprise App
- Begin Scanning a Slack for Pro and Business App
- Begin Scanning a Workday App (Beta)
- Begin Scanning a Yammer App
- Begin Scanning a Zendesk App
- Begin Scanning a Zoom App
- Reauthenticate to a Cloud App
- Verify Permissions on Cloud Apps
- Start Scanning a Cloud App
- Rescan a Managed Cloud App
- Delete Cloud Apps Managed by Data Security
- API Throttling
- Configure Classification Labels
- Microsoft Labeling for Office 365
-
-
-
- SaaS Security with Enterprise DLP
- Predefined Data Patterns on Data Security
- Proximity Keywords
- Confidence Levels
- Shared Data Profiles and Data Patterns
- Modify a Predefined Data Pattern
- Create a Custom Data Profile
- Add a File Property Data Pattern
- Create a Custom Data Pattern
- Use Exact Data Matching (EDM)
- Enable or Disable a Machine Learning Data Pattern
- Configure WildFire Analysis
- Configure Regular Expressions
- Enable or Disable a Data Pattern
- View and Filter Data Pattern Match Results
-
-
-
- What is an Incident?
- Assess New Incidents on Data Security
- View Asset Details
- Filter Incidents
- Security Controls Incident Details
- Track Down Threats with WildFire Report
- Track Down Threats with AutoFocus
- Customize the Incident Categories
- Close Incidents
- Download Assets for Incidents
- View Asset Snippets for Incidents
- Analyze Inherited Exposure
- Email Asset Owners
- Modify Incident Status
-
- What is a Data Violation?
- Assess New Data Violations on Data Security
- Configure Data Violation Alerts on Data Security
- Filter Data Violations on Data Security
- View Asset Snippets for Data Violations on Data Security
- View Data Violation Metrics on Data Security
- Modify Data Violation Status on Data Security
-
-
-
-
- What’s SaaS Security Inline?
- Navigate To SaaS Security Inline
- SaaS Visibility for NGFW
- SaaS Visibility and Controls for NGFW
- SaaS Visibility for Prisma Access
- SaaS Visibility and Controls for Panorama Managed Prisma Access
- SaaS Visibility and Controls for Cloud Managed Prisma Access
- Activate SaaS Security Inline for NGFW
- Activate SaaS Security Inline for VM-Series Firewalls with Software NGFW Credits
- Activate SaaS Security Inline for Prisma Access
- Connect SaaS Security Inline and Strata Logging Service
- Integrate with Azure Active Directory
-
-
- SaaS Policy Rule Recommendations
- App-ID Cloud Engine
- Guidelines for SaaS Policy Rule Recommendations
- Predefined SaaS Policy Rule Recommendations
- Apply Predefined SaaS Policy Rule Recommendations
- Create SaaS Policy Rule Recommendations
- Delete SaaS Policy Rule Recommendations
- Enable SaaS Policy Rule Recommendations
- Modify Active SaaS Policy Rule Recommendations
- Monitor SaaS Policy Rule Recommendations
-
- Enable Automatic Updates for SaaS Policy Rule Recommendations on Cloud Managed Prisma Access
- Import New SaaS Policy Rule Recommendations on Cloud Managed Prisma Access
- Update Imported SaaS Policy Rule Recommendations on Cloud Managed Prisma Access
- Remove Deleted SaaS Policy Rule Recommendations on Cloud Managed Prisma Access
- Manage Enforcement of Rule Recommendations on NGFW
- Manage Enforcement of Rule Recommendations on Panorama Managed Prisma Access
- Change Risk Score for Discovered SaaS Apps
-
-
-
-
- Onboarding Overview for Supported SaaS Apps
- Onboard an Aha.io App to SSPM
- Onboard an Alteryx Designer Cloud App to SSPM
- Onboard an Aptible App to SSPM
- Onboard an ArcGIS App to SSPM
- Onboard an Articulate Global App to SSPM
- Onboard an Atlassian App to SSPM
- Onboard a BambooHR App to SSPM
- Onboard a Basecamp App to SSPM
- Onboard a Bitbucket App to SSPM
- Onboard a BlueJeans App to SSPM
- Onboard a Box App to SSPM
- Onboard a Bright Security App to SSPM
- Onboard a Celonis App to SSPM
- Onboard a Cisco Meraki App to SSPM
- Onboard a ClickUp App to SSPM
- Onboard a Confluence App to SSPM
- Onboard a Contentful App to SSPM
- Onboard a Convo App to SSPM
- Onboard a Couchbase App to SSPM
- Onboard a Coveo App to SSPM
- Onboard a Crowdin Enterprise App to SSPM
- Onboard a Customer.io App to SSPM
- Onboard a Databricks App to SSPM
- Onboard a Datadog App to SSPM
- Onboard a DocHub App to SSPM
- Onboard a DocuSign App to SSPM
- Onboard a Dropbox Business App to SSPM
- Onboard an Envoy App to SSPM
- Onboard an Expiration Reminder App to SSPM
- Onboard a Gainsight PX App to SSPM
- Onboard a GitHub Enterprise App to SSPM
- Onboard a GitLab App to SSPM
- Onboard a Google Analytics App to SSPM
- Onboard a Google Workspace App to SSPM
- Onboard a GoTo Meeting App to SSPM
- Onboard a Grammarly App to SSPM
- Onboard a Harness App to SSPM
- Onboard a Hellonext App to SSPM
- Onboard an IDrive App to SSPM
- Onboard an Intercom App to SSPM
- Onboard a Jira App to SSPM
- Onboard a Kanbanize App to SSPM
- Onboard a Kanban Tool App to SSPM
- Onboard a Kustomer App to SSPM
- Onboard a Lokalise App to SSPM
- Onboard a Microsoft Azure AD App to SSPM
- Onboard a Microsoft Exchange App to SSPM
- Onboard a Microsoft OneDrive App to SSPM
- Onboard a Microsoft Outlook App to SSPM
- Onboard a Microsoft Power BI App to SSPM
- Onboard a Microsoft SharePoint App to SSPM
- Onboard a Microsoft Teams App to SSPM
- Onboard a Miro App to SSPM
- Onboard a monday.com App to SSPM
- Onboard a MongoDB Atlas App to SSPM
- Onboard a MuleSoft App to SSPM
- Onboard a Mural App to SSPM
- Onboard an Office 365 App to SSPM
- Onboard Office 365 Productivity Apps to SSPM
- Onboard an Okta App to SSPM
- Onboard a PagerDuty App to SSPM
- Onboard a RingCentral App to SSPM
- Onboard a Salesforce App to SSPM
- Onboard an SAP Ariba App to SSPM
- Onboard a ServiceNow App to SSPM
- Onboard a Slack Enterprise App to SSPM
- Onboard a Snowflake App to SSPM
- Onboard a SparkPost App to SSPM
- Onboard a Tableau Cloud App to SSPM
- Onboard a Webex App to SSPM
- Onboard a Workday App to SSPM
- Onboard a Wrike App to SSPM
- Onboard a YouTrack App to SSPM
- Onboard a Zendesk App to SSPM
- Onboard a Zoom App to SSPM
- Onboarding an App Using Azure AD Credentials
- Onboarding an App Using Okta Credentials
- Delete SaaS Apps Managed by SSPM
Onboarding an App Using Okta Credentials
To access an administrator account through Okta Single Sign On (SSO), SSPM requires
your organization's Okta subdomain and an MFA secret key.
Depending on the app that you are onboarding,
you might be accessing an administrator account through Okta Single Sign On (SSO).
To access an administrator account through Okta SSO, SSPM requires your
organization's Okta subdomain and an MFA secret key. Complete the following steps to
get this information. Depending on the app that you are onboarding, you might be
required to provide additional information during onboarding.
- Identify your Okta subdomain.Your Okta subdomain was included in the Okta login URL that was assigned to your organization. The URL that was assigned to your organization is in the format https://<your_okta_subdomain>.okta.com and often your Okta subdomain is the name of your company. However, your organization can define a custom URL that does not include your Okta subdomain. If you are an Okta administrator, you can identify the subdomain from the Okta administrator dashboard. Your subdomain is displayed in the header of the dashboard.Before you continue to the next step, make note of your Okta subdomain. You will provide this information to SSPM during the onboarding process.
- Generate and copy an MFA secret keyMFA provides an extra layer of security when accessing the Okta user account. To enable this extra layer of security, the Okta user account must be configured for MFA that uses one-time passcodes. These one-time passcodes are generated from authenticator apps such as Okta Verify or Google Authenticator by using an MFA secret key. The key is a shared secret between Okta and the authentication app. This shared secret enables Okta and the authentication app to generate matching passcodes for verification. Like an authentication app, SSPM will use the MFA secret key to generate one-time passcodes for accessing the Okta user account.If the user account is already configured for MFA, and if you know the MFA secret key value, you do not need to complete the following steps. You need only provide the MFA secret key to SSPM during the onboarding process. If the user account is not configured for MFA, or if you do not know the MFA secret key, complete the following steps.
- Log into the Okta user account.
- Locate your profile menu in the upper right corner of the page. Select.Profile menuSettings
- On the Settings page, locate the section that is labeled Extra Verification or Security Methods. This section shows the MFA methods that are available.In addition to providing SSPM with the MFA secret key, you must also configure an authentication app with the MFA secret key. Configuring an authentication app will enable the app to generate the one-time passcodes that you will need to access the account.
- Decide which authentication app you will use and download it to your cell phone.Depending on your organization, you can set up MFA for either the Okta Verify or Google Authenticator apps. Decide which of these authentication apps you will configure. This decision might be limited to the authentication apps that your organization allows, which are shown in the Extra Verification or Security Methods section of the Settings page.
- From the Okta settings page,Set upeither Okta Verify or Google Authenticator. If theSet upbutton is disabled,Edit Profileto enable the action.If Okta Verify or Google Authenticator is already enabled for MFA, but you do not know the MFA secret key, then you mustRemovethe current setup, and thenSet upthe authenticator again.
- Follow the on-screen instructions for setting up the authenticator app, but, when you are presented with a QR code that contains the MFA secret key, do not scan the it with your authentication app. Instead, manually record and enter the QR code.
- On the MFA set up page that displays the QR code, clickCan't scan?.
- If you are using Google Authenticator, continue to the next step. If you are using Okta Verify, you are redirected to a page with setup options. To display the MFA secret key as a character string,Setup manually without push notification.
- Okta displays the MFA secret key as a character string instead of as a QR code. Copy the key into a text file.Do not continue to the next step unless you have copied the MFA Secret Key. You must provide this key to SSPM during the onboarding process.
- Configure your authentication app by manually entering the MFA secret key. If you are using Okta Verify, when you are prompted to scan the QR Code,Enter key manuallyinstead. If you are using Google Authenticator, when you are following the steps to configure MFA,Enter a setup key.