Single Sign Sample Clauses
The Single Sign clause establishes that a party is required to execute a document or agreement only once, rather than signing multiple copies or versions. In practice, this means that a single, original signature is sufficient to bind the parties, and additional signatures on duplicate documents are not necessary. This clause streamlines the execution process, reduces administrative burden, and helps prevent confusion or disputes over which version of a document is the official, binding one.
POPULAR SAMPLE Copied 2 times
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:
Single Sign. ON (SSO) REQUIREMENTS Clever Google SFUSD – ADFS (Local) None Other
Single Sign. On AddOn
Single Sign. On (SSO) integration options to streamline user authentication and access to 1Password
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.
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.
Single Sign. On for ▇▇▇▇ 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.
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.
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.