Medidata Single Sign-On Integration Requirements Sample Clauses

Medidata Single Sign-On Integration Requirements. Where Customer elects to create a single sign-on (“SSO”) integration with iMedidata® (“SSO Integration”) for use with Customer’s credential authorization system, it agrees to: (i) apply minimum technical requirements and comply with the acceptable use parameters (e.g., requirements for usernames, passwords, password reset, end point maintenance, and testing environments) set forth in xxxxx://xxx.xxxxxxxx.xxx/en/medidata-policies/, as may be updated on reasonable notice by Medidata (“SSO Specifications”); (ii) promptly notify Medidata of errors or vulnerabilities discovered in Customer’s SSO Integration (to xxxxxxxx@xxxxxxxx.xxx); and (iii) assist Medidata with verifying Customer’s adherence to the SSO Specifications, including permitting an audit up to once annually on 45-day notice, or such audits as are required for cause. The SSO Integration may be terminated by Medidata on reasonable notice in its sole discretion.
Sample 1
AutoNDA by SimpleDocs

Related to Medidata Single Sign-On Integration Requirements

  • Support Requirements If there is a dispute between the awarded vendor and TIPS Member, TIPS or its representatives may assist, at TIPS sole discretion, in conflict resolution or third party (mandatory mediation), if requested by either party. TIPS, or its representatives, reserves the right to inspect any project and audit the awarded vendors TIPS project files, documentation and correspondence. Status of TIPS Members as Related to This Agreement TIPS Members stand in the place of TIPS as related to this agreement and have the same access to the proposal information and all related documents. TIPS Members have all the same rights under the awarded Agreement as TIPS.

  • Installation Requirements 7.8 We (if we install the System) or our contractor (if we procure a contractor to install the System) must:

  • New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to:

  • Documentation Requirements (a) An employee must apply for personal leave in the form required by the CEO as soon as it is reasonably practicable for the employee to make the application.

  • Design Requirements 9.2.1. Metal liner The compressive stress in the liner at zero pressure and 15 °C shall not cause the liner to buckle or crease.

  • Encryption Requirements Transfer Agent will not locally store Fund Data on any laptops or mobile devices (e.g., Blackberries, PDAs) managed by Transfer Agent.

  • Contracting Information Requirements Contractor represents and warrants that it will comply with the requirements of Section 552.372(a) of the Texas Government Code. Except as provided by Section 552.374(c) of the Texas Government Code, the requirements of Subchapter J (Additional Provisions Related to Contracting Information), Chapter 552 of the Government Code, may apply to the Contract and the Contractor agrees that the Contract can be terminated if the Contractor knowingly or intentionally fails to comply with a requirement of that subchapter.

  • Construction Requirements a) All Life and Safety and applicable Building Codes will be strictly enforced (i.e., tempered glass, fire dampers, exit signs, smoke detectors, alarms, etc.). Prior coordination with the Building Manager is required.

  • Electronic and Information Resources Accessibility and Security Standards a. Applicability: The following Electronic and Information Resources (“EIR”) requirements apply to the Contract because the Grantee performs services that include EIR that the System Agency's employees are required or permitted to access or members of the public are required or permitted to access. This Section does not apply to incidental uses of EIR in the performance of the Agreement, unless the Parties agree that the EIR will become property of the State of Texas or will be used by HHSC’s clients or recipients after completion of the Agreement. Nothing in this section is intended to prescribe the use of particular designs or technologies or to prevent the use of alternative technologies, provided they result in substantially equivalent or greater access to and use of a Product.

  • Food Service Waste Reduction Requirements Contractor shall comply with the Food Service Waste Reduction Ordinance, as set forth in San Francisco Environment Code Chapter 16, including but not limited to the remedies for noncompliance provided therein.

Time is Money Join Law Insider Premium to draft better contracts faster.