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.
Sample 1Sample 2See All (4)
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.
Sample 1Sample 2
Relying Party Obligations. As a Relying Party, you agree that:
Sample 1Sample 2
Relying Party Obligations. Relying 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.
Sample 1
Relying Party Obligations. 1. Before relying on a Certificate or a Digital Signature, Relying Parties must:
Sample 1
Relying Party Obligations. As a Relying Party, you are obligated to ensure the reasonableness of your reliance on any Information by:
Sample 1

Related to Relying Party Obligations

  • Contractor Obligations The Contractor is responsible for fully meeting all Contract obligations set forth in the OGS Centralized Contract and for providing services in accordance with the Contract and any Authorized User Agreement, Statement of Work or Purchase Order.

  • Sub-processor Obligations MailChimp shall: (i) enter into a written agreement with the Sub-processor imposing data protection terms that require the Sub-processor to protect the Customer Data to the standard required by Data Protection Laws; and (ii) remain responsible for its compliance with the obligations of this DPA and for any acts or omissions of the Sub-processor that cause MailChimp to breach any of its obligations under this DPA.

  • 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 In the event of any termination hereunder, Buyer shall return all documents and other materials furnished by Seller with respect to the Hospital Campus Real Property. No information or knowledge obtained in any investigation pursuant to this Section shall affect or be deemed to modify any representation or warranty contained in this Agreement or the conditions to the obligations of the Parties hereunder. Buyer shall keep the Hospital Campus Real Property free and clear of all mechanics’ or materialmen’s liens arising from or related to Buyer’s due diligence efforts and shall take all necessary actions, at Buyer’s sole cost and expense, to remove any such liens that encumber the Hospital Campus Real Property to the extent that the existence of such liens shall have a material adverse effect on Seller (including, without limitation, causing Seller to be in default of any of its obligations or agreements), the Hospital Campus Real Property (or any portion thereof) or the Licensed Operations.

  • Processor Obligations 4.1 The Processor may collect, process or use Personal Data only within the scope of this DPA.

  • 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.

  • 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 shall:

  • Obligations of the Licensee 5.1.1. The Licensee’s Responsibilities and Duties shall include the following, in addition to and without prejudice to other obligations under this Agreement:

  • Seller Obligations Seller shall (A) arrange and pay independently for any and all necessary costs under any Generator Interconnection Agreement with the Participating Transmission Owner; (B) cause the Interconnection Customer’s Interconnection Facilities, including metering facilities, to be maintained; and (C) comply with the procedures set forth in the GIP and applicable agreements or procedures provided under the GIP in order to obtain the applicable Electric System Upgrades and (D) obtain Electric System Upgrades, as needed, in order to ensure the safe and reliable delivery of Energy from the Project up to and including quantities that can be produced utilizing all of the Contract Capacity of the Project.

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