Skip to main content
🚀 New: AI-Powered ETA Predictions now available!Learn more →
SupplySense 360
SupplySense 360
Getting StartedUpdated 2025-01-27

SSO Configuration Guide

Step-by-step guide to configure Single Sign-On (SSO) for your organization.

Single Sign-On (SSO) allows your users to log in to SupplySense 360 using their existing corporate credentials from identity providers like Microsoft Azure AD, Okta, or Google Workspace.

Benefits of SSO

  • Simplified Access: Users log in with their existing company credentials
  • Enhanced Security: Leverage your organization's authentication policies
  • Centralized Control: Manage user access from your identity provider
  • Automatic Provisioning: New users are created automatically on first login

Supported Identity Providers

SupplySense 360 supports the following identity providers via OpenID Connect (OIDC):

  • Microsoft Azure AD / Entra ID
  • Okta
  • Google Workspace
  • Any OIDC-compliant provider

Azure AD / Entra ID Setup

Step 1: Create an App Registration

  1. Go to the Azure Portal
  2. Navigate to Azure Active Directory then App registrations
  3. Click New registration
  4. Configure the app:
    • Name: SupplySense 360 SSO
    • Supported account types: Accounts in this organizational directory only
    • Redirect URI: Select "Web" and enter your callback URL (see below)
  5. Click Register

Redirect URI Format: https://YOUR-DOMAIN.supplysense360.com/api/auth/sso/callback

Step 2: Configure Authentication

  1. In your app registration, go to Authentication
  2. Under Implicit grant and hybrid flows, check ID tokens
  3. Click Save

Step 3: Get Your Client Secret

  1. Go to Certificates and secrets
  2. Click New client secret
  3. Add a description (e.g., "SupplySense 360") and select an expiry period
  4. Click Add
  5. Important: Copy the secret value immediately - you will not be able to see it again!

Step 4: Find Your Configuration Values

  • Client ID: Found on the app Overview page as "Application (client) ID"
  • Tenant ID: Found on the Overview page as "Directory (tenant) ID"
  • Issuer URL: https://login.microsoftonline.com/YOUR-TENANT-ID/v2.0

Step 5: Configure in SupplySense 360

  1. Go to Admin then Customers then select your organization
  2. Click on SSO Configuration
  3. Enable SSO and fill in:
  4. Click Test to verify the configuration
  5. Click Save Configuration

Okta Setup

Step 1: Create an OIDC Application

  1. Log in to your Okta Admin Console
  2. Go to Applications then Applications
  3. Click Create App Integration
  4. Select:
    • Sign-in method: OIDC - OpenID Connect
    • Application type: Web Application
  5. Click Next

Step 2: Configure the Application

  1. App integration name: SupplySense 360
  2. Sign-in redirect URI: https://YOUR-DOMAIN.supplysense360.com/api/auth/sso/callback
  3. Sign-out redirect URI: https://YOUR-DOMAIN.supplysense360.com
  4. Assignments: Select appropriate user groups
  5. Click Save

Step 3: Get Your Configuration Values

After creating the app, you will see:

  • Client ID: Displayed on the app General tab
  • Client Secret: Click "Generate new secret" if needed
  • Okta Domain: Your Okta URL (e.g., your-company.okta.com)

Step 4: Configure in SupplySense 360

  1. Go to Admin then Customers then select your organization
  2. Click on SSO Configuration
  3. Enable SSO and fill in:
    • Identity Provider: Okta
    • Email Domain: your-domain.com
    • Issuer URL: https://your-company.okta.com
    • Client ID: Your Okta Client ID
    • Client Secret: Your Okta Client Secret
  4. Click Test to verify
  5. Click Save Configuration

Google Workspace Setup

Step 1: Create OAuth Credentials

  1. Go to the Google Cloud Console
  2. Select or create a project
  3. Go to APIs and Services then Credentials
  4. Click Create Credentials then OAuth client ID
  5. Configure:
    • Application type: Web application
    • Name: SupplySense 360
    • Authorized redirect URIs: https://YOUR-DOMAIN.supplysense360.com/api/auth/sso/callback
  6. Click Create

Step 2: Configure OAuth Consent Screen

  1. Go to OAuth consent screen
  2. Select Internal (for Google Workspace users only)
  3. Fill in the required information
  4. Add scopes: email, profile, openid
  5. Save

Step 3: Configure in SupplySense 360

  1. Go to Admin then Customers then select your organization
  2. Click on SSO Configuration
  3. Enable SSO and fill in:
    • Identity Provider: Google Workspace
    • Email Domain: your-domain.com
    • Client ID: Your Google OAuth Client ID
    • Client Secret: Your Google OAuth Client Secret
  4. Click Save Configuration

Generic OIDC Provider Setup

For other identity providers that support OpenID Connect:

Requirements

Your identity provider must:

  • Support OpenID Connect (OIDC)
  • Provide a well-known configuration endpoint at /.well-known/openid-configuration
  • Support the authorization code flow with PKCE

Configuration Values Needed

  • Issuer URL: The base URL of your identity provider
  • Client ID: The application/client identifier
  • Client Secret: The client secret for authentication
  • Redirect URI: Configure this in your IdP: https://YOUR-DOMAIN.supplysense360.com/api/auth/sso/callback

Optional Advanced Settings

For providers that do not follow standard OIDC conventions, you may need to specify:

  • Authorization URL: The OAuth authorization endpoint
  • Token URL: The token exchange endpoint
  • UserInfo URL: The user information endpoint

Troubleshooting

Configuration validation failed

  • Verify your Issuer URL is correct and accessible
  • Ensure the /.well-known/openid-configuration endpoint returns valid JSON
  • Check that your identity provider is not blocking requests from SupplySense 360

SSO login failed

  • Verify the Client ID and Client Secret are correct
  • Ensure the redirect URI is configured correctly in your identity provider
  • Check that the user email domain matches the configured SSO domain

User not assigned to application

  • In your identity provider, ensure users or groups are assigned to the application
  • For Azure AD, check that the user is in the correct directory
  • For Okta, verify the user is in an assigned group

Need Help?

Contact our support team for assistance with SSO configuration.

PreviousQuick Start Guide