Single Sign Sample Clauses

Single Sign. On Customer is responsible for providing specifications from target vendor in an industry standard format and securing cooperation with target vendor. Q2 agrees to honor the following pricing provided that Customer purchases via a separate sales order form no later than forty-five (45) days from the Effective Date of this Agreement:
Sample 1Sample 2
Single Sign. On Allows automatic access to Bill Pay and Order Checks without having to re-enter an Access ID and Password.
Sample 1
Single Sign. On for RSA Access Manager Allows OnBase to be configured to use authentication credentials from selected single sign‐on service vendors. Single sign‐on servicescentralize authentication and authorization across multiple applications. OnBase Web Client configurations are supported.OnBase Client and the Desktop are not supported. Appropriate Single Sign‐On service.
Sample 1
Single Sign. On for XXXX Allows OnBase to be configured to use authentication credentials from selected single sign‐on service vendors. Single sign‐on servicescentralize authentication and authorization across multiple applications. Valid Client license Appropriate Single Sign‐On service. Single Sign‐On for Central AuthenticationService (CAS) Allows OnBase to be configured to use authentication credentials from selected single sign‐on service vendors. Single sign‐on servicescentralize authentication and authorization across multiple applications. OnBase Web Client configurations are supported.OnBase Client and the Desktop are not supported. Appropriate Single Sign‐On service.
Sample 1
Single Sign. On between core Marketplace and Open Calls platforms‌ The integration between the two individual platforms, the core L4MS Marketplace and the open calls platform, a Single Sign-On functionality has been developed, that allows users to sign up and login to the L4MS Marketplace, and then use the open calls platform with the same credentials, without having to sign up or log in again. The Single Sign-On feature was implemented following the OAuth2 protocol, where the core Marketplace serves as the server side of the protocol, and the open calls platform as the client side.
Sample 1
Single Sign. On (SSO) Integration Single Sign-On (SSO) will take place during implementation. All usernames, passwords, user groups, roles, and account names will be managed locally by “Enterprise Customer” via Active Directory. All updates will be synchronized with Schoology. SSO can be established with third parties, via Schoology’s custom SSO script.
Sample 1
Single Sign. On AddOn
Sample 1
Single Sign. On and Third Party Online Services
Sample 1
Single Sign. ON (SSO) REQUIREMENTS Clever Google SFUSD – ADFS (Local) None Other
Sample 1
Single Sign. On for Custom Applications Allows OnBase to be configured to use authentication credentials from selected single sign‐on service vendors. Single sign‐on servicescentralize authentication and authorization across multiple applications. OnBase Web Client configurations are supported.OnBase Client and the Desktop are not supported. Appropriate Single Sign‐On service. Single Sign‐On for PeopleSoft Enterprise Allows OnBase to be configured to use authentication credentials from selected single sign‐on service vendors. Single sign‐on servicescentralize authentication and authorization across multiple applications. OnBase Web Client configurations are supported.OnBase Client and the Desktop are not supported. Appropriate Single Sign‐On service. Single Sign‐On for IBM Tivoli AccessManager Allows OnBase to be configured to use authentication credentials from selected single sign‐on service vendors. Single sign‐on servicescentralize authentication and authorization across multiple applications. OnBase Web Client configurations are supported.OnBase Client and the Desktop are not supported. Appropriate Single Sign‐On service.
Sample 1