Skip to main content
System StatusContact Support
VersionOne Community

Single Sign-On

This feature is available in Ultimate edition only.

editions-u.png

The content in this article applies to On-premise VersionOne instances only. If you are an On-Demand (V1 Hosted) customer, see On-Demand (V1 Hosted) System Maintenance.

SAML-based Single Sign-On (Browser SSO) is a security configuration option available in an on-demand environment. Using SAML, the Lifecycle Service Provider integrates with your Identity Provider to authenticate users when accessing VersionOne.  This eliminates the need for separate credentials when accessing the application and gives you full control over authentication, access and more flexibility with password rules for your users.

If your organization already uses SAML-based SSO and you’d like to configure your on-demand Lifecycle instance to participate, contact your Account Manager for additional details.

Enabling SSO

  1. Install Lifecycle using the default V1 authentication.
  2. Rename the 'admin' username to match the administrator's SSO username.

  3. Add the following to appSettings in user.config (or create a user.config if it doesn't already exist):

    <add key="DelegatedAuthHeader" value="HTTP_USER"/>
    
  4. Configure your SSO system to protect VersionOne virtual directory and supply the username to VersionOne via HTTP_USER header variable

  5. If creating a new user.config file, for example, its contents would be:

    <appSettings>
    <add key="DelegatedAuthHeader" value="HTTP_USER"/>
    </appSettings>
    

Once configured, Lifecycle will authenticate users based on username supplied in HTTP_USER header variable. An 'Access Denied' message displays to users who do not have a matching username defined in Lifecycle.

  • Was this article helpful?