Android™

Verify the Timestamp Server Token (if any) while Validating a CMS Signature

Demonstrates how to also validate the timestamp server token (if any) while validating a CMS signature. Android™

// Important: Don't forget to include the call to System.loadLibrary
// as shown at the bottom of this code sample.
package com.test;

import android.app.Activity;
import com.chilkatsoft.*;

import android.widget.TextView;
import android.os.Bundle;

public class SimpleActivity extends Activity {

  private static final String TAG = "Chilkat";

  // Called when the activity is first created.
  @Override
  public void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);

    boolean success = false;

    CkCrypt2 crypt = new CkCrypt2();

    //  Tell Chilkat to also validate the timestamp token if a timestamp exists in the CMS message's unauthenticated attributes.
    CkJsonObject cmsOptions = new CkJsonObject();
    cmsOptions.UpdateBool("ValidateTimestampTokens",true);
    crypt.put_CmsOptions(cmsOptions.emit());

    String outputFile = "qa_output/original.xml";
    String inFile = "qa_data/p7m/fattura_signature.xml.p7m";

    //  Verify the signature and extract the contained file, which in this case is XML.
    success = crypt.VerifyP7M(inFile,outputFile);
    if (success == false) {
        Log.i(TAG, crypt.lastErrorText());
        return;
        }

    Log.i(TAG, "Signature validated.");

  }

  static {
      System.loadLibrary("chilkat");

      // Note: If the incorrect library name is passed to System.loadLibrary,
      // then you will see the following error message at application startup:
      //"The application <your-application-name> has stopped unexpectedly. Please try again."
  }
}