How to Set Up SSO with Okta for AppSecEngineer Learning Platform

SSO Setup with Okta for AppSecEngineer: A Step-by-Step Guide

Follow these steps to configure Single Sign-On (SSO) with Okta using SAML 2.0 integration for AppSecEngineer.

Step 1: Sign in to Okta Admin Panel

  1. Log in to your Okta Admin account.
  2. Navigate to Applications → Click Create App Integration.

    Okta Applications dashboard showing AppSecEngineer listed as an active and inactive appThe image displays the Okta Applications dashboard, where the AppSecEngineer application appears in both active and inactive statuses. The interface includes options to create app integration, browse the app catalog, and assign users to an app.

Step 2: Select SAML 2.0

  1. Choose SAML 2.0 as the sign-in method.

  2. Okta interface displaying the 'Create a new app integration' window with SAML 2.0 selected.
    Click Next to continue.

Step 3: Configure General Settings

  1. In the App Name field, enter a recognizable name like AppSecEngineer-SSO.
    Okta interface displaying the 'Create SAML Integration' setup page with 'AppSecEngineer' as the app name.The image shows the Okta dashboard with the 'Create SAML Integration' page open. The setup is in the General Settings stage, where the App name is set as AppSecEngineer. There is an option to upload an App logo (optional) and a checkbox for App visibility (allowing users to hide the application icon).
  2. Click Next to proceed.

Step 4: Configure SAML Settings

  1. In the Single Sign-On URL, enter:
    https://auth.learning.appsecengineer.com/saml2/idpresponse
  2. In the Audience URI (SP Entity ID), enter:
    urn:amazon:cognito:sp:us-east-2_FJ1zCXvmb
  3. Set NameID Format to EmailAddress.
    Okta SAML Settings page with SSO URL, Audience URI, and user attributes configured for AppSecEngineerThe image displays the SAML Settings in Okta for AppSecEngineer, showing the Single Sign-On (SSO) URL, Audience URI (Amazon Cognito), Name ID format (EmailAddress), and application username settings. There is also an option to add attribute statements.

Step 5: Attribute Mapping

Map the attributes as follows:

  • Emailuser.email
  • First Nameuser.firstName
  • Last Nameuser.lastName
    Okta SAML attribute statements configuration with email, given name, and surname mappings.The image displays the attribute statements section in Okta's SAML settings. It maps the email, first name (given name), and last name (surname) to corresponding user attributes. The option to add another attribute statement is visible, along with a section for group attribute statements.

Step 6: Finalizing the Application Setup

  1. Select "This is an Internal App" and click Finish.
    Okta Create SAML Integration final step with internal app selection.Final step of Okta SAML integration with an internal app selection option.
    If you're looking for a broader SSO setup beyond Okta, check out our detailed guide on Integrating SSO (Single Sign-On) for seamless authentication across platforms."

Step 7: Retrieve Metadata URL

  1. In the Application Sign-On section, locate the Metadata URL.

    Okta SAML 2.0 sign-on settings with metadata details and relay state for Amazon Cognito.Okta SAML 2.0 sign-on configuration showing relay state and metadata URL for integration with Amazon Cognito.

  2. Copy and share this URL with the AppSecEngineer team.
Need to configure SSO with Auth0 instead of Okta? Follow our step-by-step guide on SSO Setup for AppSecEngineer with Auth0 for seamless authentication.

Step 8: Assign Users & Groups

  1. Ensure that the appropriate users or user groups are assigned to this application.
  2. Only assigned users will have SSO login permissions.
                                                                       


🎯 Next Steps:

✅ Verify the integration by logging into AppSecEngineer using SSO.
✅ If any issues arise, check user assignments and attribute mappings in Okta.


    • Related Articles

    • Enterprise API integration guide

      We provide most of the reports that are present in our dashboard as APIs which can be integrated into your own system/Business Intelligence tools or some other Dashboards/systems, which will provide insights and help track progress on your own ...
    • Integrating SSO (Single Sign-On)

      Pre-Requisites Ensure your organization uses a SAML v2.0 compliant IdP. Decide whether to enable SCIM (System for Cross-domain Identity Management) for real-time user provisioning (optional). Step 1: Enable SSO for Your Account Contact the ...
    • SCIM Integration Guide

      Login into Azure Portal, Find and go to Microsoft Entra ID service Click on Enterprise Application → New Application → Create Your Own application Name the application something recognizable such as AppSecEngineer-SCIM, select the Non-gallery option ...
    • SSO setup for AppSecEngineer with Auth0

      Note: This feature is enterprise only, kindly login with admin access to set this up Auth0 SSO SetUp Guide in order to start the SSO setup for AppSecEngineer with Auth0, follow these steps: Go to Auth0 console → Applications → Create Application ...
    • Integrate LTIAAS

      Prerequisites: An active enterprise plan with AppSecEngineer Access to moodle with same email address as registered admin on ASE platform Note: There is no data synchronization LTI 1.3 Integration: Allows enterprises to pull training content ...