Okta Master Course - Application SSO Integration

Introduction

  • Host: Kieran Tross

  • Topic: Continuation of the Octor Master course focused on the integration of OCTA apps.

  • Purpose: Discuss managing cloud-based applications through the OCTA platform.

Overview of OCTA App Integration

  • OCTA serves as a configured connection between its features like OCTA Universal Directory and external applications (e.g., Zoom, Box).

  • Applications can be integrated and displayed on a dashboard, often referred to as tiles or apps.

  • Integration Types:

    • Pre-built Integrations: Available in the OCTA Integration Network (OIN).

    • Custom Crafted Admin Apps: Proprietary applications specific to an organization.

Focus on Single Sign-On (SSO)

  • Definition of Single Sign-On (SSO):

    • SSO allows users to access multiple applications (cloud-based, on-premise, or mobile) using a single set of authentication credentials.

    • Users authenticate once to access all integrated applications seamlessly, enhancing user convenience and reducing password management complexities.

    • Example Scenario: Imagine managing 10 different applications with unique usernames and passwords—this creates a management nightmare. SSO centralizes identity management, leveraging either Active Directory credentials or OCTA credentials as the single source of truth to streamline access across applications.

SSO Integration Methods

  • Various methods available for integrating SSO:

    • Open ID Connect

    • Security Assertion Markup Language (SAML)

    • Secure Web Authentication

    • Web Services Federation

Navigating the OCTA App Catalog

  • Procedure to explore the app catalog within OCTA:

    • Access the applications section of the OCTA platform.

    • Browse available apps or filter for specific requirements.

    • Example Application: Display of how to add Zendesk integration:

    • Search for "zenes" to locate Zendesk and select "Add Integration."

    • Define application label (e.g., use "zenes") and provide the Zen desk subdomain (login details).

    • Configuration options include visibility settings (e.g., hiding the application icon or automatic login).

Sign-On Methods Configuration

  • Demonstration of configuring sign-on methods for Zendesk integration within OCTA:

    • Select SAML 2.0 settings.

    • Populate necessary metadata for Zendesk:

    • SSO URL: URL provided by OCTA.

    • Certificate Fingerprint: Security information for authentication, kept confidential.

    • Additional fields include relay state, remote logout URL, and IP address ranges for access control.

Setting Up the Integration Procedure

  • Steps for setting up the integration:

    • Log into Zendesk and enter the provided SSO information from OCTA.

    • Ensure correct setup following the view setup instructions option provided on the OCTA interface.

    • Verification involves team member authentication and configuration adjustments in Zendesk settings.

    • Important to note: The OCTA and Zendesk setup should correctly define mutual SSO configurations.

Managing Assignments

  • Configuration options in OCTA:

    • Can provision users via CSV imports or manual assignments.

    • Users or groups can be assigned access to Zendesk, enabling them to manage customer tickets.

    • Example: Assigning a group (e.g., call center team) for Zendesk access.

Conclusion

  • Closing remarks on the integration process and encouragement to engage with the content.

  • Invitation for questions or comments in the comment section.

  • Call to action: Like and subscribe to the channel (Cloud Scholars) for further learning and development.