Single Sign Sample Clauses

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. Figure 22: Testing the SSO feature - authorize
AutoNDA by SimpleDocs
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) “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.” There was an issue to support the single sign on feature in Glueing Service. It is an essential feature in order to perform grid operations for neuGRID users with their own credentials. To address this issue, the Glueing Service provides a session creation approach and uses this session information for grid operations on user’s behalf. In this approach, a user or a client of the Glueing Service needs to pass on its grid proxy just once to the Glueing Service. The user can get this proxy from his desktop fusion environment if he wants to access the Glueing Service from his terminal. Other services such as the Pipeline Service, with their portlets inside the neuGRID portal environment, can retrieve user proxy from the portal context. After receiving this proxy string, the Glueing Service stores it locally and assigns a unique identifier to it. This unique identifier is termed as session_id in the Glueing Service context. The method exposed for this purpose is named as createSession(proxy_string). The user can use this identifier in subsequent requests to the Glueing Service. On the basis of this identifier, the Glueing Service uses the corresponding user proxy certificate and performs the requested operation. With this architecture, the flow of client request to the Glueing Service and its response is shown in the following sequence diagram. The Glueing Service uses JavaGAT to perform file related operations. For the implemented prototype, a gLite adaptor has been used to test these operations on gLite-based grid infrastructure. The method ‘read’ expects a session_id, and a LFN from the user. After receiving the LFN in a service call, the Glueing Service invokes gLite adaptor using GSFile, a layer written on top of the JavaGAT, and passes on the LFN to this adaptor to perform the required operation such as read or write. The sequence diagram in figure 6 illustrates this to perform read operation on a file identified by a given LFN. Figure 6: read operation in Glueing Service
Single Sign. On and Third Party Online Services UPS offers a single sign on feature for the UPS WeChat Application using your WeChat credentials. If User elects to use User’s credentials for WeChat (the “Platform”) UPS will receive from the Platform the User’s basic information such as User’s name, email address, and any other information User permits the Platform to share with UPS now or in the future. When User engages with the Platform, User is interacting with a third party, not UPS. UPS does not endorse and has no control over the Platform. The information User shares with a Platform is subject to the Platform’s own privacy policy and User’s privacy settings on the Platform. To the maximum extent permitted by law, UPS makes no representations or warranties, express or implied, as to Platform or any other third party website or application (including the accuracy, reliability or completeness of information supplied by it or its privacy practices). If User decides to access other websites or applications, including the Platform, User does so at User’s own risk. Under no circumstances will UPS be responsible for any loss or damage resulting from User’s use of the Platform or any other third party website or application. If the Platform service becomes temporarily or permanently unavailable for any reason, if User elects to delete User’s account for the Platform, or if User unlinks User’s credentials to the Platform from User’s UPS profile maintained on the UPS WeChat Application and xxx.xxx, User will not be able to log into User’s UPS profile maintained on the UPS WeChat Application and xxx.xxx using User’s Platform credentials. In order to log in and continue using User’s UPS profile maintained on the UPS WeChat Application and xxx.xxx, User will need to log in using User’s UPS profile credentials.
Single Sign. On (SSO) is the capability to log into multiple related, but independent software systems using one username and password.
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: ********************************* Total Deposit Due $ ***** Less: pre-paid deposit paid May x, 2012 ****** Deposit Due Upon Contract Execution $ ****** Includes all implementation fees and************ months of subscription fees for Q2 Services and Third Party Services; deposit will be applied as a credit towards charges due during first ****** months of the initial term of this Agreement. Project will commence only after deposit has been received by Q2. Please remit via wire transfer according to the following wire instructions: Wire Instructions Account Name: Q2 Software, Inc. Company Address: 0000 Xxxxxxxx Xxxx., Xxxxxxxx XX, Xxxxx 000, Xxxxxx, Xxxxx 00000 Company Phone Number: 000-000-0000 ABA Routing Number: ************* Checking Account Number: *************** Bank Name: Plains Capital Bank Bank Address: 000 Xxxxxxxx Xxx., Xxxxx 000, Xxxxxx, Xxxxx 00000 AGREED AND ACCEPTED: ROCKLAND TRUST COMPANY Q2 SOFTWARE, INC. “CUSTOMER” Signature Signature Printed Name Printed Name Title Title Date Date EXHIBIT B
Single Sign. ON (SSO) REQUIREMENTS The District requires software applications support the use of SFUSD-provided Single Sign-on (SSO) credentials for students and educators to access instruction materials, preferably Clever or Google Federated Login. Which of the following will your organization be using to process SSO authentication requests? Clever Note: If Clever is used, please provide the following additional information Clever Note: If Clever is used, please provide the following additional information 1. What Clever API version does the integration support today? 2. Is the iOS application certified by Clever's partner engineering team? YES NO 3. Does the integration support student SSO? YES NO 4. Does the integration support school admin SSO? YES NO 5. Does the integration support district admin SSO? YES NO 6. Does the integration support co-teachers? YES NO 7. Does the integration support multi-site students? YES NO 8. Does the integration support multi-site teachers? YES NO 9. Does the integration support multiple classes per student? YES NO 10. Does the integration support multiple classes per teacher? YES NO 11. Does the integration have any quirks or limitations that should be kept in mind? (e.g. only certain section subjects are supported) – if yes, please explain: YES NO Google SFUSD – ADFS (Local) None Other
AutoNDA by SimpleDocs
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 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) SSO is an authentication process that enables users to access the HHR using the login credentials of their line-of-business system. Where organisations have enabled SSO functionality, the clinical system that they use will log the user directly into the HHR via SSO, using their primary log-in to identify the user’s access rights. Full user and patient auditability is retained when using this functionality. The SCW CSU, as primary Data Processor, are responsible for providing SSO functionality to participating organisations and enabling the functionality, in agreement with the clinical system supplier of the organisation who will be viewing the data. Where SSO is in use, the Data Controller is responsible for:
Time is Money Join Law Insider Premium to draft better contracts faster.