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. 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 Xxxxx’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. (SSO) Contractor’s PIMS shall support Single Sign-On through a number of federated identify standards: XXXX 2.0 (Security Assertion Markup Language) and/or Active Directory Federation Services (ADFS). County shall maintain and support ADFS.
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.
Single Sign On. CL has the ability to facilitate Single Sign-On (“SSO”) through OAuth 2.0 and Azure AD. As of the Effective date of this Agreement, CL is in the process of developing SSO using XXXX
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. Single Sign-On Service is available to UMB billing clients whose own websites allow Payors to log in and obtain their personal account information. This Service operates similarly to Web Direct except that Payors are not required to maintain separate log-in credentials to access the Hosted Payments Website. With Single Sign-On you are responsible for identifying and verifying your Payors and for ensuring the security of your website. You are not required to provide us with a Payor Account Master File if your system user interface takes payment information from the Hosted Payments Website and integrates it into your accounting system. However, you also have the option to use a Payor Account Master File.
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.
Single Sign On. Synacor will develop a process which synchronizes the usernames between xxxxxx.xxx and xxxxxxxx.xxx so customers can seamlessly go between the two sites without having to log in separately pursuant to the terms and conditions set forth in Exhibit 16. As part of such Services Synacor will link Synacor to Embarq’s Identity Management system so Synacor can access additional product information for the customers, enabling Synacor to allow user access to new products that will be integrated into the xxxxxxxx.xxx portal like Embarq Complete Contacts and Integrated Voicemail.
