Single Sign On Sample Clauses
The Single Sign On clause establishes the requirement or option for users to access multiple related systems or services using a single set of login credentials. In practice, this means that once a user logs in through a central authentication system, they can seamlessly access other integrated applications without needing to re-enter their username and password. This clause streamlines user access, enhances security by reducing password fatigue, and simplifies account management for both users and administrators.
POPULAR SAMPLE Copied 51 times
Single Sign On. The Service enables single sign-on integration. By enabling single sign-on, User is authorizing its users to access and use the Service directly from a third-party service. Such third-party service may not have the same authentication and security features as the Service. User assumes all risk and responsibility arising from the use of, and access to and from, the Service enabled through single sign-on.
Single Sign On. Insurer shall implement single sign-on between FHKC’s Enrollee portal and Insurer’s Enrollee portal at the direction of FHKC, subject to the Parties’ abilities to satisfy the security requirements of the other Party. Insurer shall cooperate with FHKC during all stages of implementing single sign-on, including any exploratory or information gathering stages. FHKC shall determine any project timeframes, including the final effective date; however, Insurer shall assist FHKC in determining reasonable timeframes by providing any information requested by FHKC.
Single Sign On. ▇▇▇▇▇▇ uses ▇▇▇▇ based single sign-on to access and operate the Services.
Single Sign On. Creating and implementing the data passing methodology for single sign on using a standard agreed to between ML and Imprev. [*] Designates portions of this document that have been omitted pursuant to a request for Confidential Treatment filed separately with the Commission. Reference Codes. Imprev will create five (5) reference codes. Reference Codes identify Marketing Material library access, logo libraries and other features. Language Support. The Marketing Center user interface is provided in US English. At its expense, Market Leader can add additional languages for the user interface as required. The Marketing Center supports the Western European character set (Latin 1). Market Leader shall be billed a Technology Development Fee for all related development if Imprev assists in modifying the user interface to a non US English language. Integration between ML & Imprev. • Imprev to support links within ML that drive a user to certain specific locations within Imprev and send End User & listing information to be used in Data Enabled Designs. • Imprev to support accepting an End User’s contact database from ML. Contact databases over [*] will be handled as follows: Imprev monitors or gets an admin notice that an End User’s contact list is over [*], Imprev permits End User upload, Imprev emails or otherwise calls out to End User (in its capacity as ML representative) the necessity to sign separate email terms and simultaneously notifies ML customer support, Imprev sends out and collects a signed email term agreement (with the form to be mutually agreed by the parties, but to be along the lines of Imprev’s standard terms but provided under ML’s name), Imprev emails ML customer support so that a record of the signed terms can be made. • Imprev to support a ‘Back’ link that sends an End User from Imprev system back to ML system. • Imprev to support a ‘Concerted Logout’ method that ensures when an End User logs out from one system, she is logged out of all systems. (available post-launch) • Imprev to send event information back to ML in order for ML to create history records for emails. After launch, event information for USPS mails sent through the Campaign Management System (CMS) to contacts will be added. Account Configuration. Imprev will make configuration changes such as not metering email, hiding the address book, and making certain elements of the End User profile read-only.
Single Sign On. We need to implement a single-sign functionality to facilitate users. Currently to invoke enactment of a workflow and access other resources, the user's certificate, key and associated passphrase are required to initiate a proxy at the Glueing Service end. To use this model the user has to provide all of these details every time a requested is made. To cater for this limitation the glueing, pipeline and other services need to be integrated with a Single Sign On service (SSO). This task will be achieved in year 3.
Single Sign On. At your request, Com Laude may provide access to its portals via Single-Sign-On (SSO). SSO involves authentication procedures that are outside of Com ▇▇▇▇▇’s control. By accessing the portals via SSO, you agree that you have reviewed and adequately mitigated against any likely security risks involved in accessing Com Laude’s portals in this way. Further, you agree that:
(i) Com Laude bears no responsibility for the security of your internal organisational authentication procedures; and (ii) you shall remain responsible at all times for keeping your login details secure and maintaining appropriate security measures across all user accounts within your control, including (but not limited to) the enforcement of two-factor authentication on any user accessing the portals via SSO.
Single Sign On. Contractor will provide integrated authentication through a single sign-on solution designated by the County.
Single Sign On. (SSO) REQUIREMENTS Google SFUSD – ADFS (Local) None Other
Single Sign On. Customers can elect to integrate with a customer supplied Single Sign On (SSO) provider for authentication and can use Cross-domain Identity Management (SCIM) for user management. More detail on SCIM is available here: ▇▇▇▇▇://▇▇▇▇.▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/articles/about-genesys-cloud-scim-identity-management/ and on SSO here: ▇▇▇▇▇://▇▇▇▇.▇▇▇▇▇▇▇▇▇▇▇.▇▇▇/articles/about-single-sign-on-sso/.
Single Sign On. 8.1 The SLA is extended to include Single Sign On (“SSO”) services for maintenance, upgrades and 24/7 monitoring of the integration between CSP and Customer production environments. The SSO provides easy access for all end-users, where users are automatically logged into their account in Comaea through the SSO integration.
8.2 The SSO integration is limited to the CSP’s technical environment and do not include the Customers technical environment or network.
8.3 The cost for SSO maintenance, upgrades and 24/7 monitoring is to be agreed at the point that the service is requested.