Document Signing Configurations
To create a new Go>Sign profile for document signing click the New button. This following screen is shown:
The configuration items are as follows:
| Items |
Description |
| Status |
A Go>Sign profile may be marked Active or Inactive. Note that an inactive profile will not be used to process requests generated by client application. |
| Profile ID |
A mandatory field which provides a system-defined unique identifier for this profile. |
| Profile Name | A mandatory unique name defined by the ADSS Server Administrator for easier recognition of the profile within the ADSS Operator Console. |
| Profile Description | This can be used to describe the profile in more detail (e.g. in which circumstances will this Go>Sign profile be used). This is for information purposes only. |
| Document Signing | Select this option if you want to create Go>Sign profile for document signing. |
| Certificate Generation | Select this option if you want to create Go>Sign profile for certificate generation using Go>Sign Desktop. Click here for certificate generation documentation. |
| PKCS#10/CSR Creation | Select this option if you want to create Go>Sign Profile for PKCS#10/CSR Creation using Go>Sign Desktop |
| Document Input Source |
Defines where the document or data to be signed is located. When this is set to "Server" the data will be passed from the business application to the ADSS Server Go>Sign Service, it will be hashed and sent to the Go>Sign Client for signing. When this is set to "Client" the data will be obtained from the browser memory, or it can read it from the user's disk drive. The Go>Sign Client will pass the data back to ADSS Server for hashing and the hash value will be returned to the Go>Sign Client for signing. For security and simplicity of the Go>Sign Client all hashing takes place within the ADSS Server Go>Sign Service. See ADSS Server Go>Sign Developers Guide section 4.3 Post Processing Functions. Note: "Server" is the default and "Client" is used for more complex integrations. |
| Document Output Source | ADSS Server Go>Sign Service creates the final output signed data. When this is set to "Server" this will be available for the business application (the application needs to call ADSS Server and request that the signed data or document is sent back. When this is set to "Client" the signed data or document will be returned so it can be made available in the browser for viewing, available to the business application or written to the user's disk drive. See ADSS Server Go>Sign Developers Guide section 4.3 Post Processing Functions. Note: "Server" is the default and "Client" is used for more complex integrations. |
See also