Skip to main content

​
SSO Settings - Enterprise Single Sign-On

Valiyou SSO settings interface for configuring Enterprise Single Sign-On with SAML, OAuth, and OpenID Connect identity providers
Plan Required: Enterprise plan only Permission Required: Admin or SSO management permission
Configure Enterprise Single Sign-On (SSO) to allow team members to authenticate using your organization’s identity provider. This advanced security feature enables seamless login through corporate credentials, centralized user management, enhanced security with multi-factor authentication (MFA), and simplified onboarding and offboarding processes. Valiyou supports SAML 2.0, OAuth 2.0, and OpenID Connect protocols with popular identity providers including Okta, Azure Active Directory, Google Workspace, OneLogin, and Auth0.

​
Supported Protocols

  • SAML 2.0 - Industry-standard authentication protocol
  • OAuth 2.0 - Modern authorization protocol
  • OpenID Connect - Identity layer built on OAuth 2.0

​
Supported Identity Providers

  • Okta
  • Azure Active Directory (Microsoft Entra ID)
  • Google Workspace
  • OneLogin
  • Auth0
  • Custom SAML/OAuth providers

​
SSO Configuration Fields

  • Provider type selection
  • Entity ID / Issuer URL
  • SSO URL / Login URL
  • Certificate upload (X.509)
  • Attribute mapping
  • JIT (Just-In-Time) provisioning toggle

​
Benefits of SSO

  • Single set of credentials for all tools
  • Centralized user management
  • Enhanced security (MFA, conditional access)
  • Simplified onboarding/offboarding
  • Compliance with corporate policies
Contact Support: SSO configuration requires technical setup. Contact support@valiyou.com for assistance with SSO setup and testing.

​
SSO Login Flow

  1. User clicks “Sign in with SSO” on login page
  2. Redirected to identity provider
  3. Authenticates with corporate credentials
  4. Redirected back to Valiyou with session
  5. Automatically logged in (or account created via JIT)

​
Common Use Cases

​
Enabling SSO for Team (Enterprise)

  1. Contact support@valiyou.com to begin SSO setup
  2. Provide identity provider details
  3. Work with support to configure SAML/OAuth
  4. Test SSO login with admin account
  5. Enable JIT provisioning (optional)
  6. Roll out SSO to team
  7. Communicate SSO login instructions

​
Troubleshooting

​
SSO Not Working

Common Issues:
  • Incorrect Entity ID or SSO URL
  • Certificate expired or invalid
  • Attribute mapping incorrect
  • JIT provisioning disabled
Solution:
  • Contact support@valiyou.com for SSO troubleshooting
  • Verify identity provider configuration
  • Test with admin account first
  • Check browser console for errors

​
Frequently Asked Questions

Single Sign-On (SSO) allows team members to authenticate to Valiyou using your organization’s identity provider instead of separate login credentials. When users click “Sign in with SSO,” they’re redirected to your corporate identity provider (like Okta or Azure AD), authenticate with their corporate credentials, and are automatically logged into Valiyou. This provides enhanced security, centralized user management, and simplified access control.
Valiyou supports all major enterprise identity providers including Okta, Azure Active Directory (Microsoft Entra ID), Google Workspace, OneLogin, Auth0, and any custom SAML 2.0 or OAuth 2.0 compliant provider. The platform supports three authentication protocols: SAML 2.0 (industry standard), OAuth 2.0 (modern authorization), and OpenID Connect (identity layer on OAuth 2.0).
Enterprise SSO requires an active Enterprise plan subscription and Admin or SSO management permissions. You’ll also need access to your organization’s identity provider configuration, including Entity ID/Issuer URL, SSO URL/Login URL, X.509 certificate, and attribute mapping details. Contact support@valiyou.com to initiate the SSO setup process.
SAML 2.0 (Security Assertion Markup Language) is an industry-standard authentication protocol that exchanges authentication and authorization data between your identity provider and Valiyou. When configured, users authenticate through your SAML provider, which sends a secure assertion to Valiyou confirming the user’s identity. This enables secure, password-less authentication using your existing corporate credentials.
JIT (Just-In-Time) provisioning automatically creates user accounts in Valiyou when someone logs in via SSO for the first time. When enabled, employees can access Valiyou immediately after SSO setup without manual account creation. The system uses attribute mapping from your identity provider to populate user details like name, email, and department during automatic account creation.
Yes, Azure Active Directory (now called Microsoft Entra ID) is fully supported for SSO configuration. Valiyou integrates with Azure AD using SAML 2.0 or OpenID Connect protocols. You’ll configure Valiyou as an enterprise application in your Azure AD tenant, provide the required URLs and certificates, and map user attributes. Contact support for Azure AD specific setup guidance.
Common SSO issues include incorrect Entity ID or SSO URL configuration, expired or invalid X.509 certificates, improper attribute mapping, or disabled JIT provisioning. First, verify your identity provider configuration matches the values in Valiyou SSO settings. Test with an admin account before rolling out to all users. Check browser console for error messages. For persistent issues, contact support@valiyou.com with specific error details.
SSO enhances security through multiple mechanisms: centralized authentication reduces password-related vulnerabilities, enables multi-factor authentication (MFA) enforcement through your identity provider, supports conditional access policies (like IP restrictions or device compliance), provides centralized audit logs of authentication attempts, simplifies offboarding by disabling access from a single location, and ensures compliance with corporate security policies.
OAuth 2.0 and OpenID Connect configuration requires similar steps to SAML setup. You’ll provide your OAuth provider’s authorization endpoint, token endpoint, client ID, client secret, and configure attribute mapping. OpenID Connect adds an identity layer to OAuth 2.0 for user authentication. Contact support@valiyou.com for protocol-specific configuration guidance and testing assistance.
Yes, you can implement SSO in phases. Start by configuring SSO with support assistance, test thoroughly with admin accounts, enable JIT provisioning if desired, then gradually communicate SSO login instructions to team members. Users can continue using password authentication during the transition until everyone is comfortable with SSO. You can also configure SSO as optional or required based on your security policies.