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. (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. 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) is the capability to log into multiple related, but independent software systems using one username and password.
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. As the proper function of a learning ecosystem is based on the interactions between a wide range of applications and tools, the main challenges for every educational organisation are enabling seamless communication across these applications, merging existing applications implemented in educational organisations with new solutions and enhancing the User Experience (UX) by providing single authentication. The BEACONING solution aims to facilitate the execution of learning services and transform them into a new simplified digital experience for teachers, students, and parents by initiating a paradigm shift in organising and conducting interactions via technology and improving collaborations between stakeholders. Learning services provided by BEACONING should appear to their end users as compact and unified entities, regardless of the medium of interactions. In this way, educational organisations enable synergic effects for end users, making their experience with technology more efficient. Transactions that are part of this type of interactions can be divided into three groups: - The first group of transactions corresponds to the student level and includes the interactions with game-based technologies. Collecting feedback can help estimate the effects of the changes and enable the discovery of good practices. - The second group of transactions corresponds to the teacher level and relates to managing gamified learning experiences and unified learning analytics. - The third group of transactions corresponds to the teacher level and includes the exchange of information about student progress for various learning activities. It also includes feedback from parents The BEACONING platform includes single sign-on services that components can use to authenticate and authorize users. These are part of the core service component and are implemented based on the OAuth 2.0 open standard. OAuth 2.0 is a protocol that allows distinct parties to share information and resources in a secure and reliable manner [1]. The use of OAuth 2.0 allows: - Federated identity. A service provider allows authentication of a user using their identity with another service provider. Users do not need to create individual accounts. The user only needs to maintain a single user account, which gives them access to several service providers. For example, a BEACONING student can use the same account to play the minigames in the Gamified Lesson Paths and also access their learning analytics dashboard...
Single Sign On. At Customer’s option, Provider shall ensure the Product supports the industry standard single- sign-on (“SSO”) method designated by Customer.
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. Contractor will provide integrated authentication through a single sign-on solution designated by the County.
