We use cookies on our site to analyze traffic, enhance your experience, and provide you with tailored content.

For more information visit our privacy policy.

Relying Party Obligations Sample Clauses

Relying Party Obligations. Before placing any reliance on a Time-Stamp, the Relying Party shall verify that the TST has been correctly signed and that the private key used to sign the TST has not been revoked. If this verification takes place after the end of the validity period of the certificate, the Relying Party should follow the guidance denoted in Annex D of ETSI EN 319 421. The Relying Party should take into account any limitations on usage of the time-stamp indicated by this Subscriber Agreement, the QV-TSP/PS, the TSA Disclosure Statement and any other precautions documented by QuoVadis.
AutoNDA by SimpleDocs
Relying Party Obligations. When relying on a time-stamp token, the Relying Party shall verify that the time-stamp token was correctly signed and that the private key used to sign the time-stamp has not been revoked. During the validity period of the TSU's certificate, the validity of the signing key can be verified on the SwissSign CRL. If the verification takes place after expiry of the certificate's validity period, the relying party shall check whether the employed hash function, algorithms, and cryptographic key lengths can still be deemed secure. For further terms and conditions applicable to Relying Parties, refer to the TSA Disclosure Statement in the SwissSign TSA Policy and to other agreements between the parties.
Relying Party ObligationsRelying Parties shall rely on a certificate that has been issued by the PMA if (and only if): • the certificate has been used for the purpose for which it has been issued, as described in the Certificate Policies; • the Relying Party has verified the validity of the digital certificate, using procedures described in the X.509 standard and this section 5; • the Relying Party has established trust in the certificate by verifying the certificate path to a trust point, in accordance with the guidelines set by the X.509 standard; Relying parties must check revocation status of any certificates on which they wish to rely, by accessing the relevant CRLs and ARLs from the published source at the time of certificate validation. Relying parties must check the authenticity and integrity of the certificate status information by: • verifying that the CRL, ARL has been digitally signed using the Private Key corresponding with the digital certificate purported to have been used; • verifying the validity of the digital certificate, using procedures described in the X.509 standard; and • establishing trust in the CA who issued a certificate by verifying the certificate path in accordance with the guidelines set by the X.509 standard. If necessary, and if practical, the Relying Party shall check the subsequent CRL, ARL or certificate status message issued after the digital signature has been created to verify the on-going validity of the certificate that has been used. If a CRL, ARL or certificate status service is temporarily not available, a certificate has no status or value until the CRL, ARL or certificate status service becomes available once more. The Relying Party can make an informed decision as to whether to reject the certificate, or whether to accept the increased risk, responsibility and consequences of accepting the certificate.
Relying Party Obligations. As a Relying Party, you agree that: a. You will only rely on an EV Certificate if: (1) all of the checks described in Section 1 are successful (i.e. the EV Certificate has not expired or been revoked at the time of your reliance), and (2) that reliance upon the EV Certificate is reasonable under the circumstances, as defined by "Reasonable Reliance" in Section 5 below. b. You will not rely on an EV Certificate if any Certificate in the Certificate Chain has been revoked. c. You will independently assess and determine whether the use of the EV Certificate for your purposes is appropriate under the circumstances; d. You are solely responsible for deciding whether or not to rely upon or otherwise use the information provided by DigiCert in an EV Certificate; e. Your use of an EV Certificate or any CRL is governed by this Agreement and DigiCert's Certification Practice Statement for Extended Validation Certificates. f. You alone shall entirely bear the legal consequences of your failure to perform or comply with the Relying Party obligations set forth in this Agreement.
Relying Party Obligations. The Relying Party shall:
Relying Party Obligations. As a Relying Party, you agree that: a. You will only rely on a Certificate or Site Seal if: (1) all of the checks described in Section 1 are successful (i.e. the Certificate or Site Seal has not expired or been revoked at the time of your reliance), and (2) that reliance upon the Certificate or Site Seal is reasonable under the circumstances, as defined by "Reasonable Reliance" in Section 5 below. b. You will not rely on a Certificate or Site Seal if any Certificate in the Certificate Chain or if the Site Seal has been revoked. c. You will independently assess and determine whether the use of the Certificate or Site Seal for your purposes is appropriate under the circumstances; d. You are solely responsible for deciding whether or not to rely upon or otherwise use the information provided by DigiCert in a Certificate or Site Seal; e. Your use of a Certificate, Site Seal or any CRL is governed by this Agreement and the applicable DigiCert CPS. f. You alone shall entirely bear the legal consequences of your failure to perform or comply with the Relying Party obligations set forth in this Agreement.
Relying Party Obligations. The Relying Party shall: a) Be solely responsible for deciding whether or not to rely on the information provided by the TSP; b) Check the validity, suspension and revocation status of a Certificate on which the Relying Party may wish to rely, as well as all the Certificates in the Certificate Chain. If any of the Certificates in the Certificate Chain is expired or has been suspended or revoked, any reliance on an Electronic Signature performed with such Certificate is solely at the Relying Party’s own risk. To this end the Relying Party shall on the occasion of each reliance refer to the CRL or the OCSP in accordance with the CP; c) Rely on the Certificate only if all the checks described in the previous paragraphs are successful and if reliance upon the Certificate is reasonable under the circumstances. If the circumstances indicate a need for additional assurance, it is the Relying Party’s responsibility to obtain such assurances for such reliance to be deemed reasonable; d) Be subject to any limitations on the usage of the Certificates indicated either in the Certificates or in the CP or in this Agreement; e) Notify the TSP immediately, if the Relying Party becomes aware of or suspects that a Private Key has been compromised; 1 The Relying Party Agreement is available on the repository which is directly linked from the Certificate. f) Take all the other precautions prescribed in this Agreement or the CP, and as may be reasonably required to rely upon any information or services based on the Certificates or otherwise provided by the TSP.
AutoNDA by SimpleDocs
Relying Party Obligations. 1. Before relying on a Certificate or a Digital Signature, Relying Parties must: (a) Validate the Certificate and Digital Signature (including by checking whether or not it has been Revoked, Expired or Suspended) in accordance with section 2.1.4.1; and (b) ascertain and comply with the purposes for which the Certificate was issued and any other limitations on reliance or use of the Certificate which are specified in the Certificate, the CPS or this CP. 2. If a Relying Party relies on a Digital Signature or Certificate in circumstances where it has not been Validated in accordance with paragraph 2. 1.4.1 it assumes all risks with regard to it (except those that would have arisen had the Relying Party Validated the Certificate) and is not entitled to any presumption that the Digital Signature is effective as the signature of the Subscriber or that the Certificate is valid. 3. Relying Parties must also comply with any other relevant obligations specified in this CP including those imposed on the entity when it is acting as a Subscriber. 2.1.4.1 Validating Digital Signatures* 1. Validation of a Digital Signature is undertaken to determine that: (a) the Digital Signature was created by the Private Key Corresponding to the Public Key listed in the Certificate of the person affixing their Digital Signature to the information (the ‘ Signer’); and (b) that the associated information has not been altered since the Digital Signature was created. 2. Validation of a Digital Signature is performed by applications following this process: (a) Establishing a Certificate Chain for the Certificate used to sign the information – In the case of a Public Hierarchy this involves confirming that the CA who Issued the Certificate is a Subordinate CA of the VGR. In the case of a Private Hierarchy it involves confirming that the CA who issued the Certificate is trusted by the Relying Party;
Relying Party Obligations. As a Relying Party, you are obligated to ensure the reasonableness of your reliance on any Information by: (i) Determining that the certificate will be used for an appropriate purpose (ii) Checking the status of a certificate in which you want to rely by downloading the latest version of the ARL/ CRL available at xxxx://xxx.xxxxxx.xxx.xx/crlnew.aspx to verify the certificate has not been revoked or suspended. (iii) Verifying the certificate validity period. (iv) Utilizing the appropriate software and/or hardware to perform digital signature verification.

Related to Relying Party Obligations

  • Third Party Obligations 3.1. The THIRD PARTY shall:- 3.1.1. not divulge the Confidential Information to any party other than as provided for in this Confidentiality Agreement; 3.1.2. use the Confidential Information only for the purposes necessary in providing the services for which he is engaged by the AUTHORITY; and 3.1.3. make no commercial use of the Confidential Information or any part thereof. 3.2. Notwithstanding the foregoing, the THIRD PARTY shall be entitled to make any disclosure required by law of the Confidential Information and shall notify the AUTHORITY of so doing in accordance with the provisions of paragraph 6.

  • Contractor Obligations After receipt of the Notice of Termination and except as otherwise directed by the State, the Contractor shall immediately proceed to: a. To the extent specified in the Notice of Termination, stop work under the Contract on the date specified. b. Place no further orders or subcontracts for materials, services, and/or facilities except as may be necessary for completion of such portion(s) of the work under the Contract as is (are) not terminated. c. Terminate and cancel any orders or subcontracts for related to the services, except as may be necessary for completion of such portion(s) of the work under the Contract as is (are) not terminated. d. Transfer to the State all completed or partially completed plans, drawings, information, and other property which, if the Contract had been completed, would be required to be furnished to the State. e. Take other action as may be necessary or as directed by the State for the protection and preservation of the property related to the contract which is in the possession of the contractor and in which the State has or may acquire any interest. f. Make available to the State all cost and other records relevant to a determination of an equitable settlement.

  • Surety Obligations No Borrower or Subsidiary is obligated as surety or indemnitor under any bond or other contract that assures payment or performance of any obligation of any Person, except as permitted hereunder.

  • Developer Obligations In accordance with applicable NYISO requirements, Developer shall maintain satisfactory operating communications with Connecting Transmission Owner and NYISO. Developer shall provide standard voice line, dedicated voice line and facsimile communications at its Large Generating Facility control room or central dispatch facility through use of either the public telephone system, or a voice communications system that does not rely on the public telephone system. Developer shall also provide the dedicated data circuit(s) necessary to provide Developer data to Connecting Transmission Owner and NYISO as set forth in Appendix D hereto. The data circuit(s) shall extend from the Large Generating Facility to the location(s) specified by Connecting Transmission Owner and NYISO. Any required maintenance of such communications equipment shall be performed by Developer. Operational communications shall be activated and maintained under, but not be limited to, the following events: system paralleling or separation, scheduled and unscheduled shutdowns, equipment clearances, and hourly and daily load data.

  • Buyer Obligations During the Delivery Term, Buyer shall arrange and be responsible for transmission service, including risk of transmission outage or curtailment, from the Delivery Point and bear all risks and costs associated with such transmission service, including, but not limited to, any transmission outages or curtailment. During the Delivery Term, Buyer shall Schedule or arrange for Scheduling Coordinator services with its Transmission Providers to receive the Product at the Delivery Point. During the Delivery Term, Buyer shall be responsible for all CAISO costs and charges, electric transmission losses and congestion from the Delivery Point.

  • Secured Party Performance of Debtor Obligations Without having any obligation to do so, the Administrative Agent may perform or pay any obligation which any Grantor has agreed to perform or pay in this Security Agreement and the Grantors shall reimburse the Administrative Agent for any amounts paid by the Administrative Agent pursuant to this Section 8.4. The Grantors’ obligation to reimburse the Administrative Agent pursuant to the preceding sentence shall be a Secured Obligation payable on demand.

  • Obligations of Receiving Party Receiving Party shall hold and maintain the Confidential Information in strictest confidence for the sole and exclusive benefit of the Disclosing Party. Receiving Party shall carefully restrict access to Confidential Information to employees, contractors and third parties as is reasonably required and shall require those persons to sign nondisclosure restrictions at least as protective as those in this Agreement. Receiving Party shall not, without the prior written approval of Disclosing Party, use for Receiving Party's benefit, publish, copy, or otherwise disclose to others, or permit the use by others for their benefit or to the detriment of Disclosing Party, any Confidential Information. Receiving Party shall return to Disclosing Party any and all records, notes, and other written, printed, or tangible materials in its possession pertaining to Confidential Information immediately if Disclosing Party requests it in writing.

  • Litigation and Contingent Obligations There is no litigation, arbitration, governmental investigation, proceeding or inquiry pending or, to the knowledge of any of their officers, threatened against or affecting the Borrower or any of its Subsidiaries which could reasonably be expected to have a Material Adverse Effect or which seeks to prevent, enjoin or delay the making of any Loans. Other than any liability incident to any litigation, arbitration or proceeding which could not reasonably be expected to have a Material Adverse Effect, the Borrower has no material contingent obligations not provided for or disclosed in the financial statements referred to in Section 5.4.

  • CONTRACTOR OBLIGATION Contractor shall identify and mark the precise portion(s) of the relevant page(s) of any records provided to Enterprise Services that Contractor believes are statutorily exempt from disclosure and identify the precise statutory basis for exemption from disclosure. In addition, if, in Contractor’s judgment, certain portions of such records are not statutorily exempt from disclosure but are sensitive because particular portions of Contractor’s records (NOT including pricing) include highly confidential, proprietary, or trade secret information (or the equivalent) that Contractor protects through the regular use of confidentiality or similar agreements and routine enforcements through court enforcement actions, Contractor shall identify and mark the precise portion(s) of the relevant page(s) of any records that include such sensitive information.

  • Client Obligations 3.1 The Client warrants and represents that: 3.1.1 it shall co-operate with Centaur as required for the proper performance of the Services; 3.1.2 it shall provide, for Centaur, its agents, subcontractors, consultants and employees, in a timely manner and at no charge, access to the Client's premises during normal office hours (being Monday – Friday 8am – 6pm), office accommodation, data and other facilities as is reasonably required by Centaur or any of them for the proper performance of the Services; 3.1.3 all information it has provided to Centaur in relation to the Services as at the date of the Order Form is accurate, complete and is not misleading and it shall provide, in a timely manner, such further information and Client Material as Centaur may require for the proper performance of the Services, and ensure that such information and Client Material is accurate, complete and not misleading; 3.1.4 it shall be responsible (at its own cost) for preparing and maintaining the relevant premises for the supply of the Services; 3.1.5 it shall inform Centaur of all health and safety rules and regulations and any other reasonable security requirements that apply at any of the Client's premises; 3.1.6 it shall only use the Services for internal business purposes and, without prejudice to the foregoing, shall not use the Services, the Deliverables or any Centaur Materials to develop a product or service that competes with any of the products or services provided by Centaur; 3.1.7 the Client Materials shall not infringe any third party rights, including any third party Intellectual Property Rights; and 3.1.8 it shall obtain and maintain all necessary licences and consents and comply with all relevant legislation in relation to the Services, before the date on which the Services are to start. 3.2 If Centaur's performance of its obligations under this Agreement is prevented or delayed by any act or omission of the Client, its agents, subcontractors, consultants or employees, Centaur shall not be liable for any costs, charges or losses sustained or incurred by the Client that arise directly or indirectly from such prevention or delay.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!