Guide: Setting Up Single Sign-On (SSO) Using Okta

Logging in with Okta

Admin Setup & User Guide for SSO Access

Want your team logging in via Okta? Here’s how to set it up and how users can access the platform once it’s ready.


Step 1: In Your Okta Admin Console

  1. Go to your Okta Admin Console.
  2. Create a new App Integration.
  3. Select OIDC - OpenID Connect as the sign-on method.
  4. Select Web Application as the Application type.
  5. Name the app: GoldPhish ( or something similar).
  6. Ensure the Authorization Code grant type is checked.✅
  7. Under Client Authentication, choose Client Secret.
  8. For Sign-in redirect URIs, enter a temporary placeholder for now.

    http://localhost/callback ( We'll get the real one in Step 3)

  9. Save the app for now and note down your:

    - Client ID

    - Client Secret

    - Okta Authority URL (Issuer URL - e.g. https://yourcompany.okta.com )


Step 2: In the GoldPhish Platform

  1. Log in to GoldPhish.
  2. Navigate to Settings → SSO → Okta.
  3. Enter your Okta Authority URL.
  4. Paste in the Client ID from Okta.
  5. Paste the Client Secret from Okta.
  6. Click Save.


Step 3: Get Your Actual Redirect URI

  1. Once saved, the platform will now display your specific Sign-in Redirect URI. It will look something like:

https://app.goldphish.com/signin-oidc-[your_company_id]

  1. Copy this full URL.

Step 4: Back in Okta – Update Redirect URI

  1. Go back to your Okta Admin Console
  2. Edit the Goldphish application integration you created in Step 1.
  3. Go to the Sign-in redirect URIs section.
  4. Replace the temporary(http://localhost/callback ) with the actual URI you copied from Goldphish in Step 3.
  5. Save the Okta application settings.

✅ Setup complete!


How Users Log In with Okta

Once you’ve completed the setup above, users can log in by following these steps:

  1. Access the platform by going to https://app.goldphish.com
  2. Enter their email address.
  3. Click the “Sign in with Okta” button.
  4. They'll be redirected to Okta for authentication and then back to the security awareness training platform.

Note:

  • Users need to be created and exist on the platform, and have a valid license assigned within the platform before they can successfully log in using Okta SSO.
  • Check that your Issuer Authority has the proper scope assigned for our app - at least okta.users.read
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us