CMS/CAdES Signing Attributes

This page is used to configure the CMS/CAdES signature settings that will be used by the Go>Sign applet.

The configuration items are as follows:

Items

Description

CMS Signature Type

A mandatory field to select the CMS signature type that will be produced by this profile. See the Supported Signature Types section for more details for the types of signatures supported by Go>Sign Service.

Signature/Document Relationship

This field defines how the signature will be placed in the signed CMS. Currently only Enveloping relationship is supported.

Hashing Algorithm

The selected hashing algorithm is used as part of the signature generation process. Following are the supported hashing algorithms:

SHA1
SHA2 (SHA224, SHA256, SHA384, SHA512)
SHA3 (SHA224, SHA256, SHA384, SHA512)

EPES Signatures

Explicit Policy Based Electronic (EPES) signature settings are only available for the CAdES Signature types. By enabling the check box Add Signature Policy Identifier, the Go>Sign profile can be used to produce (EPES) signatures where a signature policy OID, URI and user notice are added in the digital signature as specified below.

1. Signature Policy Object ID

Provide the Signature Policy OID to be added for EPES signatures.

2. Signature Policy URI

Provide the Signature Policy URI to be added for EPES signatures.If there is no Policy URI defined inside the Go>Sign profile then EPES configurations should be made in policy.properties file located at: [ADSS Installation Directory]/service/

Open this file in any text editor and enter policy OID and path to the policy document

e.g. 1.2.3.4.5 = "F:/Policy_File"

The ADSS Go>Sign Service can retrieve the signature policy document in either one of the following ways:

Using Policy URI defined in Go>Sign profile. The ADSS Go>Sign Service will use this policy URI to retrieve the online available policy document and its hash value will be calculated and embedded in the signed properties of the signature.
Using locally configured signature policy document. The ADSS Go>Sign Service will use this text file pointer to retrieve the locally saved policy document, hash and embed it in the signed properties of the signature.

3. Signature Policy User Notice

Provide the user notice to be added to the EPES signatures.

Clicking the Next button will display the Key Store Settings page.