Skip to main content

SSO Setup Guide

NoClick supports SAML 2.0 Single Sign-On (SSO) for enterprise organizations. This guide covers setup with popular identity providers including Okta, Azure AD, and others.

Prerequisites

  • A NoClick enterprise account
  • Admin access to your identity provider (Okta, Azure AD, etc.)
  • Your organization slug from NoClick

Supported Features

  • SP-Initiated SSO - Users start login from NoClick and are redirected to your identity provider
  • IdP-Initiated SSO - Users start login from your identity provider dashboard
  • JIT (Just-In-Time) Provisioning - User accounts are automatically created in NoClick on first SSO login

Okta Setup

1

Add NoClick from App Catalog

  1. Sign in to your Okta instance as an administrator
  2. Navigate to ApplicationsApplications and click Browse App Catalog
  3. On the Browse App Integration Catalog page, search for and select NoClick
  4. Click Add Integration
2

Get Metadata URL

  1. Go to the Sign On tab of the NoClick application
  2. Copy the Metadata URL (looks like https://your-domain.okta.com/app/.../sso/saml/metadata)
3

Configure NoClick

  1. Log in to NoClick as an organization admin
  2. Go to SettingsOrganizationSSO
  3. Paste the Okta Metadata URL
  4. Click Enable SSO
4

Assign Users

  1. In Okta, go to your NoClick app → Assignments
  2. Assign users or groups who should have access

Supported Attributes

The NoClick OIN application is pre-configured to send the following attributes via SAML assertion:

Azure AD Setup

1

Create Enterprise Application

  1. Go to Azure Portal → Azure Active Directory
  2. Select Enterprise applicationsNew application
  3. Click Create your own application
  4. Name it “NoClick” and select Integrate any other application (Non-gallery)
2

Configure SAML

  1. Go to Single sign-on → Select SAML
  2. Edit Basic SAML Configuration:
3

Configure Attributes

Edit Attributes & Claims:
4

Get Metadata URL

In the SAML Certificates section, copy the App Federation Metadata Url
5

Configure NoClick

  1. Log in to NoClick as an organization admin
  2. Go to SettingsOrganizationSSO
  3. Paste the Azure AD Metadata URL
  4. Click Enable SSO

Other Identity Providers

For other SAML 2.0 compatible identity providers (OneLogin, Google Workspace, JumpCloud, etc.), use these values:

Required Attributes

Testing SSO

  1. Go to noclick.com/auth/sso
  2. Enter your organization slug
  3. You’ll be redirected to your identity provider
  4. After authentication, you’ll return to NoClick

IdP-Initiated Login

  1. Log in to your identity provider dashboard
  2. Click the NoClick app tile
  3. You’ll be redirected directly to NoClick
IdP-initiated login requires the Default RelayState to be configured in your identity provider. Without it, you’ll see a “SAML RelayState is not a valid UUID or URL” error.

Troubleshooting

This occurs with IdP-initiated SSO when RelayState isn’t configured. Set the Default RelayState in your IdP to:
Users are automatically added to your organization when they first log in via SSO. Ensure:
  • The user’s email domain matches your organization’s SSO domain
  • The SSO provider is correctly linked to your organization
Verify the ACS URL in your IdP matches exactly:
Ensure the Entity ID / Audience URI matches:

Support

Need help configuring SSO? Contact us at support@noclick.com