LogoLogo
  • Home
  • Integration & SDKs
    • Web / Browser Push
      • Wordpress Integration Steps
      • Wix Integration Steps
      • Safari
        • Safari on Desktop
        • Safari on Mobile (iOS / iPadOS)
      • SDK
        • SDK Methods
        • SDK Events
        • Customizing Prompt CSS
        • AMP Support
        • E-Commerce / Abandoned Cart
    • Native App Push
      • Apple / iOS
        • P8 Key or P12 Cert Setup
        • SDK: Swift / Obj-C
          • Activity Tracking
          • Deep Linking
          • Live Activities
          • App Messages
          • Identity Synchronization
          • SDK Methods
          • SDK Delegates
        • SDK: React Native
        • SDK: Flutter
        • Advanced
          • Self-Managed Integration
        • iOS SDK Changelog
      • Android
        • Firebase App Setup
        • SDK: Kotlin / Java
          • Deep Linking
          • Activity Tracking
          • App Messages
          • Identity Synchronization
          • SDK Methods
          • SDK Callbacks
          • Live Activities
        • SDK: React Native
        • SDK: Flutter
        • Advanced
          • Self-Managed Integration
        • Android SDK Changelog
      • React Native
        • Android: Firebase App Setup
        • iOS: P8 Key or P12 Cert Setup
        • SDK: React Native
          • Deep Linking
          • Activity Tracking
          • Subscriber Matching
          • Live Activities
          • App Messages
          • SDK Methods
      • Flutter
        • Android: Firebase App Setup
        • iOS: P8 Key or P12 Cert Setup
        • SDK: Flutter
          • Deep Linking
          • Activity Tracking
          • Subscriber Matching
          • Live Activities
          • App Messages
          • SDK Methods
  • API
    • API Access Management
    • API Reference
  • Platform
    • Dashboard
    • Notifications
      • A/B Testing
      • Custom Buttons
      • Notification Previews
      • Inline Segmentation
      • Notification Templates
      • Macros
      • Native App Push Notifications
    • App Messages
    • Segments
      • Custom Geo Segmentation
    • Campaigns
    • Insights
    • User Management
    • Organizations
      • Multi-Factor Authentication
      • Single Sign On
        • Google Workspace
        • Microsoft Azure AD
        • Okta Workforce
      • Multi-Domain Notifications
      • Multi-Domain Segments
      • API Access
    • Multi-Channel Notifications
  • Info Center
    • Launch Guide & Best Practices
      • Landing Domain Whitelist
    • Web / Browser Push
      • Common Questions
      • Browser Support
      • Retrieve Push User ID
      • Not Getting Prompted
      • Not Receiving Notifications
      • How to Unsubscribe
    • Native App Push
      • Retrieve Push User ID
    • Workflow Planning
Powered by GitBook
On this page
  • In Okta Admin: Create an Okta OIDC Application
  • Pushly: Create the Okta Identity Provider
  1. Platform
  2. Organizations
  3. Single Sign On

Okta Workforce

Instructions for setting up Okta as your Identity Provider

PreviousMicrosoft Azure ADNextMulti-Domain Notifications

Last updated 2 months ago

In Okta Admin: Create an Okta OIDC Application

An administrator for your company's Okta Workforce needs to log in to the Admin portal and follow the steps below to create an OIDC Application.

Select Applications > Applications, and Create App Integration.

Select Create New App

Choose OIDC as the Sign-in method. Choose Web Application as your Application Type.

Click the Next button

Enter "Pushly" for for the App integration name

Under Sign-in redirect URIs enter the following value:

https://identity.pushly.com/login/callback

Under Sign-out redirect URIs enter the following value:

https://identity.pushly.com

If you are asked for an Initiate Login URI you may enter the following value:

https://platform.pushly.com

For Controlled access choose the appropriate option for your organization. Note that the users will still need to be created via the Pushly platform before they are able to log in even if you choose to allow everyone in your organization access via this application.

Click the Save button

On the next page copy both the Client ID and the Client Secret. The user creating the integration in the Pushly platform will need both of these values.

Pushly: Create the Okta Identity Provider

Next, click the Security tab, and click the Add Provider button.

Choose Okta Workforce from the Provider Type dropdown.

The Okta domain should be entered including the .okta.com portion. For example: yourdomain.okta.com

Fill in the Client ID and Client Secret that was generated in the first step of this documentation.

Within the Associated Domains text area enter each domain name that your organization will be using to to log in via Okta on a separate line. For example, if your email address is example@yourdomain.com then you would enter yourdomain.com

In addition to the Client ID and Client Secret you will also need to provide the Okta Domain. The Okta Domain is located in the top right of the Admin console or you can follow to retrieve the Okta domain.

Now that you have your Okta Domain, Client ID, and Client Secret you can log into the platform and page.

Once the provider has been successfully created you can begin to the platform. Any user invited that has an email address that matches one of the emails provided in Email Domains will be sent through Okta for authentication.

these instructions
inviting users
navigate to your Organization Settings