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 (SSO)
Single Sign. On (SSO)
1) Ensuring users are aware of the AUA. The Data Processor will make the AUA available to all organisations.
2) Implementing best practice such as providing standards for password composition and frequency of change to avoid confidentiality breaches.
3) Prohibiting staff from sharing passwords or leaving workstations unlocked when unattended.
4) Ensuring the starters and leavers policy restricts access to the clinical system appropriately and thus restricts access to the HHR. The organisation accepts full responsibility for the actions of its employees when using Single Sign-On and understands that a full audit trail is available detailing all staff members who have accessed patient records. In the event that the organisation is not using SSO, the responsibilities set out in this section 6.2 will not apply to this agreement.
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 (SSO) is the capability to log into multiple related, but independent software systems using one username and password.
Single Sign. On Allows automatic access to Bill Pay and Order Checks without having to re-enter an Access ID and Password.
Single Sign. On and Third Party Online Services
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.
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.
