• Standard PDF Signature
• PDF signature with embedded timestamp
• PDF signature with embedded timestamp and revocation information

• PAdES-BES (Part 3 - PAdES Enhanced )
• PAdES-BES with embedded timestamp
• PAdES-LT (Long term availability of validation data)
• PAdES-LTV (Part 4 - Long Term)

• Use an existing blank signature field in the target document:

If the document already has a blank signature field, then the name of the signature field can be specified using this option. When ADSS Server signs a PDF document using this signing profile it will then search for this signing field and embed the signature details within that field. This is also a good way of positioning the signature in an exact location rather than just the default locations mentioned above. 

Note: Signature field names are case-sensitive so ensure you enter a valid field name as used in your documents, e.g. field1 and Field1 are not the same.

Signature Appearance

Select one of the PDF Signature Appearances already generated as mentioned in the section PDF Visible Signatures.

Target Signature Field Name

Specify the name of a blank signature field (already existing in the document). If the filed name is specified in the request then that field will be signed but if field name is missing in the document signing request then a field name mentioned in this text box will be signed. If a field name not specified in the request nor found the one specified in this text box then an error will be returned.

Use this prefix to generate the incremental field names

If this option is turned on in the Go>Sign Profile then service uses an algorithm to automatically identify a field name to be signed i.e. Go>Sign service automatically checks field name e.g. " Signature1", if it is a blank field then enforces user to sign it and if already signed then enforce user to sign another field which is "Signature2" and so on.

Note: This feature only works when SharePoint server is integrated with the Go>Sign Service.

• Use a PDF editor to draw signature field(s) as required:

Create empty field signatures using the PDF. Sig Locations. These configurations will then be used while signing the document, ADSS Server Go>Sign Service will create the empty signature fields with field names and the signature appearance allocated to those empty signature fields. Set the PDF Signature Locations settings to create the empty signature fields with names as mentioned and located in the PDF editior. Set the Default Appearance Name which will embed the appearance and signer's details on the signature field when signed.

• If you want some other font to embed then you need to put the font in the [ADSS-Server-Installation-Dir]/fonts directory and then refer it in the signature appearance designer.
• For optimization reasons, only those characters which are used in the Signature Appearance are taken from the Font file and embedded
• If font is already embedded in the document prior to the signing then the font is not re-embedded.
• In order to use non-English characters this option should be enabled for visible signatures so that those characters are shown properly in the signature appearance

• Server: If the Server is selected then signature will be produced on the server side by the signing service configured in Service Settings tab.

• Client: If the Client is selected then signature will be produced by the Go>Sign applet on the client machine.

• Mobile: If the Mobile is selected then signature will be produced on the mobile device by the Mobile signature service configured in Service Settings tab

• Enveloping
• Detached

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

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.

• No changes allowed:
  This means that no further changes can be made to the document or its fields.
• Form fill-in and digital signatures:
  This option allows any existing forms fields to be filled and any existing signature fields to be signed.
• Annotations, form fill-in and digital signatures:
  This option allows annotations to be made on the document and any existing forms fields to be filled and any existing signature fields to be signed.