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
- Go to your Okta Admin Console.
- Create a new App Integration.
- Select OIDC - OpenID Connect as the sign-on method.
- Select Web Application as the Application type.
- Name the app: GoldPhish ( or something similar).
- Ensure the Authorization Code grant type is checked.✅
- Under Client Authentication, choose Client Secret.
For Sign-in redirect URIs, enter a temporary placeholder for now.
http://localhost/callback
( We'll get the real one in Step 3)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
- Log in to GoldPhish.
- Navigate to Settings → SSO → Okta.
- Enter your Okta Authority URL.
- Paste in the Client ID from Okta.
- Paste the Client Secret from Okta.
- Click Save.
Step 3: Get Your Actual Redirect URI
- 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]
- Copy this full URL.
Step 4: Back in Okta – Update Redirect URI
- Go back to your Okta Admin Console
- Edit the Goldphish application integration you created in Step 1.
- Go to the Sign-in redirect URIs section.
- Replace the temporary(
http://localhost/callback
) with the actual URI you copied from Goldphish in Step 3. - 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:
- Access the platform by going to https://app.goldphish.com
- Enter their email address.
- Click the “Sign in with Okta” button.
- 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