ARX CoSign Web App Version 7.5 Digital Signature Software User Guide

PDF

Dokumen

CoSign Web App
Version 7.5
--------------------------------
User Guide
Notice
This manual contains information that is proprietary to ARX (Algorithmic Research) Ltd. No
part of this manual may be reproduced in any form whatsoever without prior written approval
by ARX (Algorithmic Research) Ltd.
ARX (Algorithmic Research) Ltd. reserves the right to revise this publication and make any
changes without obligation to notify any person of such revisions and changes.
For further information, contact ARX (Algorithmic Research) Ltd.
Trademarks
CoSign Central Enterprise, CoSign Central FIPS, CoSign Web App, MiniKey, and CryptoKit
are trademarks of ARX (Algorithmic Research) Ltd. Other names are trademarks or registered
trademarks of respective owners and are used solely for identification purposes.
ARX (Algorithmic Research) Ltd, Tel. 1-866-EASY-PKI (327-9754) Site: www.arx.com
&copy; Copyright 2015 ARX (Algorithmic Research) Ltd.
All rights reserved.
CoSign Web App – User Guide
Pub. Date 08.15
Pub. No. CSN.WBAPP.INS.USR V7.5.08.15
Table of Contents
Chapter 1: Overview ...................................................................................................................................... 1
Requirements for Data Authentication Systems ........................................................................................................ 1
Introduction to CoSign .............................................................................................................................................. 2
Environments Supported by CoSign .................................................................................................................. 2
Applications that Work with CoSign.................................................................................................................. 3
CoSign Components ........................................................................................................................................... 3
CoSign Guides........................................................................................................................................................... 4
Intended Audience..................................................................................................................................................... 5
Organization of this Guide ........................................................................................................................................ 5
Chapter 2: Introduction to CoSign Web App .............................................................................................. 7
About CoSign Web App............................................................................................................................................ 7
Advantages of CoSign Web App ....................................................................................................................... 7
Integration with Document Management Solutions .................................................................................................. 8
Integration with External Identity Providers ............................................................................................................. 8
Chapter 3: Installing and Deploying the CoSign Web App ........................................................................ 9
CoSign Web App Installation.................................................................................................................................... 9
Installing and Configuring the CoSign Client .................................................................................................... 9
Installing the CoSign Web App Component .................................................................................................... 13
Configuring the Mail Server............................................................................................................................. 18
Configuring IIS for Kerberos Ticketing ........................................................................................................... 19
Configuration Required if PDF Forms are Used .............................................................................................. 19
Uninstalling the CoSign Web App .......................................................................................................................... 32
Chapter 4: Using CoSign Web App for Signing and Validating Documents ......................................... 33
Logging in to the CoSign Web App ........................................................................................................................ 33
Selecting a Document .............................................................................................................................................. 35
Selecting a File from a Cloud-Based File storage Service ............................................................................... 36
Viewing and Signing Documents ............................................................................................................................ 37
Viewing Pages .................................................................................................................................................. 39
Using PDF forms.............................................................................................................................................. 40
Signing a PDF Document ................................................................................................................................. 41
Signing Office 2007/2010/2013 Documents .................................................................................................... 43
Viewing Signature Details................................................................................................................................ 46
Validating Signatures .............................................................................................................................................. 47
Post-Signing Actions ............................................................................................................................................... 48
Signing in a Point of Sale Mode of Operation......................................................................................................... 50
Chapter 5: Adding Graphical Signatures and Modifying User Settings ................................................. 54
Adding Graphical Signatures .................................................................................................................................. 54
Modifying User Settings.......................................................................................................................................... 56
Logging off the CoSign Web App ........................................................................................................................... 58
Chapter 6: Signing Documents from Cloud-based File Storage Services ............................................. 59
i
Signing Documents from Dropbox .......................................................................................................................... 59
Signing Documents from OneDrive ........................................................................................................................ 60
Signing Documents from Google Drive .................................................................................................................. 61
Invoking the Signature Operation from Within Google Drive ......................................................................... 62
Signing Documents from Box ................................................................................................................................. 64
Invoking the Signature Operation from Within Box ........................................................................................ 65
Chapter 7: Configuring the CoSign Web App ........................................................................................... 67
Modifying CoSign Web App Parameters ................................................................................................................ 67
Modifying Image Setting Parameters ............................................................................................................... 67
Defining SMTP Settings .................................................................................................................................. 68
Defining Extended Authentication Settings ..................................................................................................... 68
Defining API Integration Settings .................................................................................................................... 71
Defining General Settings ................................................................................................................................ 71
Configuring CoSign Web App in Passive ADFS Mode – Using the WS Federation Protocol ............................... 73
Configuring Web App for ADFS with WS Federation Protocol ...................................................................... 74
Running the Microsoft Federation Utility ........................................................................................................ 75
Configuring CoSign Web App in SAML2 Protocol Mode ..................................................................................... 80
Configuring CoSign ADFS to use the SAML2 protocol .................................................................................. 80
Running the Saml2ConfigUtility ...................................................................................................................... 80
Configuration at the Identity Provider System ................................................................................................. 83
Configuring CoSign Web App to use Microsoft Active Directory Kerberos authentication ................................... 84
Setting Web App’s web.config File ................................................................................................................. 84
Using the setspn utility to establish a Kerberos based authentication scheme.................................................. 84
Using Internet Explorer to Access CoSign Web App Based on Kerberos Ticketing ....................................... 85
Using Google Chrome to access CoSign Web App based on Kerberos Ticketing ........................................... 86
Configuring CoSign Web App to Work with PDF Forms ....................................................................................... 86
Integrating with Cloud-Based File Storage Services ............................................................................................... 87
Defining Cloud Storage Settings ...................................................................................................................... 87
Creating an Application for Enabling Access to User Accounts in the Cloud ................................................. 88
Index.............................................................................................................................................................. 99
ii
Chapter 1: Overview
Over the last four decades, the biggest challenge of IT departments in many organizations was
moving to a paperless work environment. Seemingly, there was tremendous success in this
regard. Today, most transactions in the business world are performed electronically:
 Documents are written using word processing programs.
 Messages are sent via email.
 Inventories and purchases are tracked using Enterprise Resource Planning (ERP) systems.
 Medical information is stored in Electronic Medical Record (EMR) systems.
Although these transactions are performed in a paperless environment, organizations have still
not managed to find an easy way to get rid of the paper used for data authentication (signing
the authenticity of the data). Today, although organizations have invested large amounts of
funds and other resources in creating paperless environments, their workers are still printing
every transaction, signing it, and saving the printed copy. These organizations require a digital
method for data authentication.
By moving to a viable electronic data authentication system, organizations can reduce their
printing, archiving, shipping, and handling costs. In addition, better and more competitive
customer service can often be provided.
Requirements for Data Authentication Systems
A viable data authentication system must meet the following specifications:
 Security – The system must ensure that no one other than the data creator can tamper with
or change the data in any way.
 Third-party validation – The system must enable any third party to validate the
authenticity of the data. If a dispute arises between the parties (the data creator and
recipient), any third party must be able to validate the data authenticity in order to settle
the dispute.
 System independence – Data authentication must be independent of the system that
created the data. Users must be able to validate the authenticity of the data using a known
standard that is independent of any specific system.
 Validation over time – Users must be able to validate data authenticity at any point in
time. Authenticity cannot expire at any point.
Currently, the only data authentication method known to support all of these requirements is
the Public Key Infrastructure (PKI) method of authenticating data, simply called “digital
signatures”.
1
1
CoSign Web App User Guide
Introduction to CoSign
CoSign is a PKI-based, off-the-shelf digital-signature solution that can be integrated with a
wide range of applications. In this way, CoSign enables organizations to embed digital
signatures in various documents, forms, and transactions. CoSign is a turnkey, hardware-based
solution that is easily and quickly deployed in the network and provides cost-effective digitalsignature capabilities for the organization.
CoSign includes all the components needed for PKI-based digital-signature deployment. You
do not need to install any other device or integrate any other component for the system to
work.
Environments Supported by CoSign
CoSign integrates with leading user management systems, including Microsoft Active
Directory and a variety of LDAP (Lightweight Directory Access Protocol) based directories,
such as IBM Tivoli. This integration ensures no overhead in managing the digital-signature
system and signature credentials (i.e., the private keys that are needed in a PKI environment),
solving one of the main problems of legacy digital-signature systems. System managers,
network managers, and end-users can continue to use the IT infrastructure in the same manner
as before CoSign was installed.
CoSign stores the signature credentials in a secure server, ensuring that the signer has
exclusive access to his or her signature credentials, while still maintaining a centrally managed
solution. This is necessary in order to fulfill the security requirement of the data authentication
system.
Another option is to use the CoSign Cloud service. An organization can register its users to
the service and thus enable them to digitally sign content without having to deploy the CoSign
appliance on the organizational premises.
2
1
Overview
Applications that Work with CoSign
An increasing number of applications can work with CoSign as their digital-signature layer
without needing any further integration, including:
 Microsoft Office 2007/2010/2013 (Word and Excel)
 Microsoft InfoPath 2007/2010/2013
 Adobe Acrobat
 Microsoft SharePoint 2007/2010/2013
 XML
 TIFF files
 Word Perfect
 Microsoft Outlook and Outlook Express
 Adobe Server forms (for signing web forms)
 AutoCAD
 Lotus Notes
 Microsoft BizTalk
 FileNet eForms
 Verity Liquid Office
 ERP systems (e.g., SAP)
 OpenText
 Oracle
 Crystal Reports
 Web applications
 Any application that has a print option can use CoSign to generate a PDF file and sign it.
For information on using CoSign with other applications, contact ARX technical support.
CoSign Components
CoSign includes the following components:
 CoSign appliance – The CoSign appliance hardware and software, connected to the
organization’s network.
 Client – The CoSign Client software, installed on the users’ computers.
 Administrator – The CoSign Administrative software that includes the CoSign Microsoft
Management Console (MMC) snap-in, installed on the administrative computer.
3
1
CoSign Web App User Guide
 CoSign Connector for SharePoint – This connector enables adding digital signature
functionality to documents managed by Microsoft SharePoint, or using digital signatures
within any workflow procedure that is based on Microsoft SharePoint.
 CoSign Web App – This application is deployed in the Microsoft Web Server of the
organization and enables users to sign documents without installing any client component.
CoSign Web App can use either the local CoSign appliance or the CoSign Cloud
environment for performing digital signature operations.
Applications can interact with the CoSign Web App and add a digital signature to
documents using a web based interface.
 CoSign Mobile App – This mobile application, which can be installed on Android-based
devices or Apple iOS devices, enable users to sign documents using their mobile devices.
The mobile devices interface directly with the CoSign appliance via a CoSign RESTful
interface.
The CoSign Mobile App can interface with either the CoSign Cloud, the organizational
CoSign appliance, or CoSign’s Trial system.
 CoSign Cloud – A CoSign Cloud-based application that provides digital signature
services to users who register for the services. The CoSign Cloud supports single users as
well as groups of users.
 CoSign Signature APIs – Developers can use local and network APIs to integrate their
applications with CoSign Central appliances and the CoSign Cloud service.
CoSign Guides
CoSign documentation includes the following guides:
 CoSign Administrator Guide – Provides all the information necessary for an administrator
to install and manage the CoSign appliance in the various environments in which CoSign
can operate.
 CoSign User Guide – Provides all the information necessary for an end user to use
CoSign. Includes information about special add-ins for various applications such as
Microsoft Office.
 CoSign Connector for SharePoint User Guide – Provides all the information necessary for
implementing and using the CoSign Connector for SharePoint.
 CoSign Web App User Guide – Provides all the information necessary for deploying
CoSign Web App in the organization’s environment.
 CoSign Signature APIs Developer’s Guide – Provides all the information necessary for a
developer to integrate their application with CoSign.
 CoSign Mobile App Deployment Guide – Provides all the information necessary for
deploying CoSign Mobile App.
4
1
Overview
Intended Audience
This guide is intended for users wishing to implement the CoSign Web App. It is assumed that
readers have prior knowledge of CoSign.
Organization of this Guide
This guide is organized as follows:
 Chapter 1: Overview – Provides an overview and introduction to CoSign.
 Chapter 2: Introduction to CoSign Web App – Provides an introduction to CoSign Web
App.
 Chapter 3: Installing and Deploying the CoSign Web App – Describes how to install and
deploy CoSign Web App.
 Chapter 4: Using CoSign Web App for Signing and Validating Documents – Describes
how to use CoSign Web App.
 Chapter 5: Adding Graphical Signatures and Modifying User Settings – Describes how
each end-user can add graphical signatures and modify various user settings such his/her
signature appearance.
 Chapter 6: Signing Documents from Cloud-based File Storage Services – Describes the
end user experience for the following Cloud-based file storage services: Dropbox,
OneDrive, Google Drive, and Box.
 Chapter 7: Configuring the CoSign Web App – Describes how to customize the CoSign
Web App.
5
Chapter 2: Introduction to CoSign Web App
About CoSign Web App
Using CoSign Web App, users can digitally sign and validate documents without having to
install any client software. Instead, the signature operation uses the CoSign appliance or
appliances that were configured as part of the CoSign Client installation within the CoSign
Web App platform. You can optionally configure CoSign Web App to use the CoSign
appliances deployed in the Cloud.
CoSign Web App can be used from a wide variety of devices including iPads, iPhones,
Samsung Galaxy smart phones, etc. CoSign Web App serves many users in parallel.
CoSign Web App supports the following document types:
 PDF files.
Note that the PDF file must be no larger than 30 MB.
In addition, password protected PDF files are not supported yet.
 Microsoft Word (.docx and .doc) and Microsoft Excel (.xlsx and .xls) documents.
 MS documents that contain no signature fields are converted to PDF format when they
are loaded to the CoSign Web App.
 You can globally configure whether MS documents that contain at least one signature
fields are converted to PDF when loaded, or remain in their original format.
Note that the maximum supported file size is 30 MB, or 200 pages. Even files that are
close to the maximum limit may not load properly.
Starting from CoSign version 7.5, the CoSign Web App can be configured to upload forms
based on PDF files. The end user can enter data in the various fields. The end user’s
signature applies also to the specific data entered in the form’s fields.
Advantages of CoSign Web App
No database – The CoSign Web App does not include nor does it depend on a database
deployed in the web server. This means that it can be easily deployed and upgraded to a new
version.
High availability – It is very easy to create a high availability farm containing several web
servers, each hosting a CoSign Web App, for signing documents through a web interface.
No memory footprints – The CoSign Web App manages all files and other elements such as
graphical images in memory, and does not leave any footprints of files or other sensitive data
in the local hard disk of the CoSign Web App’s platform.
7
2
CoSign Web App User Guide
End User Authentication – The end user can be authenticated to the CoSign Web App using
either a user ID&amp;password mechanism, or an the Active Directory Kerberos ticketing
mechanism.
The end user can also be authenticated by an external Identity Provider. For more information
see Integration with External Identity Providers.
Integration with Document Management Solutions
The CoSign Web App can be integrated with applications such as a document management
application. In these types of scenarios, the application uses a special plug-in that performs a
Sign with CoSign operation. When an end user wishes to view a file and sign it, the end-user is
redirected to the CoSign Web. After signing is complete, the document management
application retrieves the signed file from the CoSign Web App.
The exact interface between the application and the CoSign Web App is described in the
CoSign Web App API section of the CoSign Programmers Guide.
In this type of usage, the CoSign Web App is named CoSign Web Agent.
Integration with External Identity Providers
The CoSign Web App can be integrated with External Identity Providers (IDP) such as
Microsoft ADFS.
In the context of using an IDP, the CoSign Web App (together with the CoSign Appliance) is
considered a Service Provider (SP).
In these cases, the end user is authenticated based on the External Identity Provider
mechanism, and the proof of authentication (that is, a SAML ticket) is forwarded to CoSign
for establishing a sustained end user account in CoSign.
Up to CoSign Web APP version 7.5, the only possible External Identity Provider was based on
Microsoft ADFS using the the WS Federation protocol. Starting from CoSign version 7.5, it is
also possible to use solutions.
It is also possible to integrate the CoSign Web Agent with an External Identity Provider.
8
Chapter 3: Installing and Deploying the CoSign Web
App
This chapter describes how to:
 Install CoSign Web App.
 Deploy CoSign Web App.
CoSign Web App Installation
CoSign Web App can be installed as a web component using the following Web Server
product:
 Microsoft IIS version 7 and above on a computer running Windows 2008 R2 and above.
Both administrative operations and user operations are based on web-based applications, thus
the end user does not have to install any software on the end PC. However, a CoSign Client
must be installed on the server on which the CoSign Web App component is installed. The
recommended order of installation is:
1. Installing and Configuring the CoSign Client.
2. Installing the CoSign Web App Component.
Installing and Configuring the CoSign Client
CoSign Web App accesses CoSign through the CoSign client installation. Therefore, before
installing the CoSign Web App component, you must:
1. Install a CoSign Client version 7.1 or above on the server that will host the CoSign Web
App component.
The CoSign Web App can only work with a CoSign Appliance version 6.2 or
above.
In addition, it is mandatory to have .NET Framework 4 installed on the hosting
platform.
2. Configure the CoSign client for optimal usage by the CoSign Web App. Refer to
Configuring the CoSign Client for CoSign Web App.
9
3
CoSign Web App User Guide
Configuring the CoSign Client for CoSign Web App
To configure the CoSign Client to work with CoSign Web App:
1. Access the CoSign control panel by selecting Start  Programs  ARX CoSign 
CoSign Control Panel. The CoSign Control panel appears.
2. Select Client Configuration. The CoSign configuration utility’s main window appears.
3. Click
to the left of the Client node.
4. Click the Appliances node.
Figure 1 CoSign Configuration Utility – Client Configuration – Appliances Parameters
5. In the Appliances screen:
a. Add the CoSign appliance IP or DNS name to the Appliance list.
b. If the list contains more than one appliance to provide high availability, you must
specify the first one as the Preferred appliance.
10
Using CoSign Web App for Signing and Validating Documents
3
c. If you would like to use the CoSign appliances that are deployed in the Cloud, enter
the following addresses:
 cosignred.arx.com
 cosignblue.arx.com
In addition, mark “cosignred.arx.com” as the Preferred appliance.
d. Check the Client Optimization checkbox.
e. If CoSign is deployed in an Active Directory environment, in the Prompt for logon
method drop-down select either of the following:
f.

User Pwd Server Side (AD/LDAP)

SSPI Used Pwd Client Side (AD)
If CoSign is deployed in an LDAP environment, in the Prompt for logon method
drop-down select User Pwd Server Side (AD/LDAP).
g. If CoSign is integrated with an External Identity provider (such as ADFS or another
Identity Provider that uses SAML2 protocol), in the Prompt for logon method
drop down select SAML Server Side.
6. Select File  Apply (save to registry) to apply the changes.
7. Click the Login dialog node.
11
3
CoSign Web App User Guide
Figure 2 CoSign Configuration Utility – Client Configuration – Login Dialog Parameters
8. In the Login dialog screen:
a. Uncheck the Permit known applications only checkbox.
b. Select Disable login dialog.
9. Select File  Apply (save to registry) to apply the changes.
10. Click the Timeouts node.
12
Using CoSign Web App for Signing and Validating Documents
3
Figure 3 CoSign Configuration Utility – Client Configuration – Timeout Parameters
11. In the Timeouts screen:
 Set the Configuration reload interval to 0.
 It is recommended to reduce the Connect failure block time to 30.
12. Select File  Apply (save to registry) to apply the changes.
13. Select File  Exit to exit the CoSign configuration utility.
Note: Following any update to the CoSign Client configuration it is recommended to
perform a reset by running an iisreset command so the new parameters will take effect.
Installing the CoSign Web App Component
To install the CoSign Web App component:
1. Deploy the CoSign Web App package to a directory in the Web Server.
2. Launch the Internet Information Services (IIS) Manager program that manages the
Microsoft Web Server.
13
3
CoSign Web App User Guide
3. Right click Sites in the Connections pane and select Add Web Site.
Figure 4 Internet Information Services (IIS) Manager
The Add Web Site window appears.
Figure 5 Add Web Site Window
14
Using CoSign Web App for Signing and Validating Documents
3
4. Perform the following:
a. In the Site name field, enter a name for this web site. The recommended name is
CoSignWeb.
b. In the Application pool field:
 If you are using a Windows 2012 system, select ASP .NET v4.5.
 Otherwise, select ASP .NET v4.0.
If you are unable to select the application pool ASP.NET v4.0, configure
ASP .NET v4.0 as part of the Microsoft IIS deployment (refer to Microsoft
documentation for instructions).
c. In the Physical path field, select the location in the server's hard disk where the
CoSign Web App will be deployed. For example: c:\inetpub\CoSignWebApp.
d. In the Host name field, define a host name (such as sign.xxx.com), or leave the field
empty.
e. In the Type field that is in the Binding section, select HTTP or HTTPS.
For initial testing purposes you can use the HTTP protocol, but on a production
system HTTPS should be used in order to secure the communication between the
user's browser and the web server, which handles the uploaded documents and the
user's credentials.
f.
In the Port field, specify a port number. For testing purposes you can use port 80.
g. If you selected HTTPS as the Binding type, the screen refreshes and an SSL
Certificate field appears. In the SSL Certificate field select an already uploaded SSL
certificate and a server key that will be used to identify this web site. For more
information on how to enroll for an SSL key and certificate and upload them to the
Microsoft IIS web server, please refer to Microsoft documentation.
15
3
CoSign Web App User Guide
Figure 6 Add Web Site Window – Specifying an SSL Certificate for the HTTPS Protocol
5. Click OK. The Web site is deployed.
16
Using CoSign Web App for Signing and Validating Documents
3
6. If you selected HTTPS as the Binding type:
a. Select the new site under Sites in the Connections pane.
Figure 7 Sites Node in Internet Information Services (IIS) Manager
b. Click SSL Settings in the right pane (Figure 7). The SSL Settings window appears.
c. Check the Require SSL checkbox.
Note: Whether you choose to use HTTPS or HTTP communication, make sure there is
connectivity between users and the CoSign Web App as well as communication
between the CoSign Web App and the CoSign appliance. If there are any networking
related issues such as a firewall, users will not be able to communicate with CoSign
Web App, and CoSign Web App will not be able to interface with the CoSign
appliance.
17
3
CoSign Web App User Guide
Redirecting HTTP to HTTPS
If you specified HTTPS connection to the CoSign Web App, you can redirect all HTTP
connections as follows:
1. Select the new site under Sites in the Connections pane (Figure 7).
2. Click Error Pages in the right pane. The Edit Custom Error Page window appears.
Figure 8 Edit Custom Error Page
3. Enter 403 in the Status code field.
4. Select Respond with a 302 redirect, and enter the URL of the HTTPS web site.
Configuring the Mail Server
As part of the CoSign Web App’s flow of operation, the CoSign Web App can send signed
documents through emails to recipients. To enable this option, you must configure the SMTP
server settings, as described in Defining SMTP Settings.
You can optionally configure the Windows Server platform to include an SMTP server by
turning on the SMTP Server feature (refer to Microsoft documentation). If you do so, make
sure to setup the SMTP server so it will restart following every startup of the server machine.
18
Using CoSign Web App for Signing and Validating Documents
3
Configuring IIS for Kerberos Ticketing
To enable the end user to authenticate using the Kerberos ticketing mechanism, IIS and the
platform on which the CoSign Web App is installed, must be configured as follows:
Settings in the Domain:
1. The machine on which the Web App and IIS are installed should be part of the Microsoft
Domain.
2. Go to the machine properties in Active Directory, and enable delegation by selecting the
Web App server Properties &gt; Delegation tab &gt; Trust this computer for Delegation to
any Service (Kerberos only).
Settings in IIS:
Set the following Web Server Settings:
1. In Authentication:
a. Enable Windows Authentication, and disable all other Authentication methods.
b. In Authentication, for Windows Authentication, choose Advanced Settings and
Enable Kernel Mode Authentication.
2. In Bindings, make sure the host name of the Web App site will be the same as the
computer name of the Web Server that will run it.
Refer to Chapter 7: Configuring the CoSign Web App for additional configuration actions
related to using the Kerberos Ticketing mechanism.
Configuration Required if PDF Forms are Used
If you wish to use PDF forms, CoSign implementation is based on a product called RAD PDF.
The RAD PDF product requires deploying Microsoft SQL on the application server.
Follows the instructions in the following sections:
 Installing an SQL Server
 Configuring the SQL Server
 Installing RAD PDF
19
3
CoSign Web App User Guide
Installing an SQL Server
1. Make sure at least .NET Framework 4 is installed on the hosting platform.
2. Install an SQL Server 2008R2 or above. Keep the default settings in all installation steps,
except in the following steps:
a. When required to indicate whether to install a new SQL server or to upgrade an SQL
server, select the option of installing a new SQL Server .
Figure 9 SQL Server Installation Center - Installation
20
Using CoSign Web App for Signing and Validating Documents
3
b. When required to enter a name for this SQL server instance, the recommended name
to enter is COSIGN.
Figure 10 SQL Server Installation – Instance Configuration
21
3
CoSign Web App User Guide
c. When required to select the authentication mode, select Windows authentication
mode. Make sure to use the administrator of the local machine.
Figure 11 SQL Server Installation – Database Engine Configuration
3. After installation is complete, make sure to install the SQL Server Management Studio.
You can download it free from the Microsoft website.
Configuring the SQL Server
Perform the following tasks:
1. Create a RadPdf Database instance to manage CoSign RadPdf data
2. Enable the IIS Service Account that runs Web App to Access the RadPdf Database
3. Create Tables in the RadPdf Database
Create a RadPdf Database instance to manage CoSign RadPdf data
Perform the following to create the RadPdf database instance that keeps information as part of
the Form Filling process.
1. Launch the SQL Server Management Studio.
2. Choose the SQL server instance you created in Installing an SQL Server, and click
Connect.
22
Using CoSign Web App for Signing and Validating Documents
3
Figure 12 Connecting to SQL Server
3. Right click Databases in the Object Explorer pane and select New Database.
Figure 13 Selecting to Create a new SQL Database
4. In the DB field enter the name RadPdf and confirm.
23
3
CoSign Web App User Guide
Enable the IIS Service Account that runs Web App to Access the RadPdf Database
The service account in IIS that will run Web App should also have access to the RadPdf
database. To enable it to do so:
1. In the SQL Server Management Studio, in the left explorer window, expand your server’s
Security &gt; Logins.
Figure 14 Viewing SQL Server Logins
24
Using CoSign Web App for Signing and Validating Documents
3
2. Search for the service account that is used to run Web App (in this case, NT
AUTHORITY\NETWORK SERVICE).
If you do not find the service account (for example, if you are using the App Pool
identity), you can either:
a. Modify the service account in IIS to one of the listed services.
or
b. Add the current service account to the list in Management Studio, as follows:
 Right click the Logins directory and choose New Login…:
Figure 15 Viewing SQL Server Logins
 Enter the login name. In anApp Pool Identity case it should look like the following
if ASP.NET v4.0 is the name of your pool:
Figure 16 Entering a new SQL Server Login
 When finished, click OK.
The service account should appear on the list.
25
3
CoSign Web App User Guide
3. Right click the relevant SQL account and select Properties. In the Properties window,
click User Mapping. You should see a list of all the databases existing in the server:
Figure 17 SQL User Mapping – Databases
4. Check the RadPdf server.
5. In the bottom of the User Mapping window, check the public and db_owner
memberships:
Figure 18 SQL User Mapping – Database Role Memberships
6. Click OK.
7. Close the SQL Server Management Studio.
26
Using CoSign Web App for Signing and Validating Documents
3
Create Tables in the RadPdf Database
1. Under the CoSignExpress directory, locate radpdf.sql.
2. Double click radpdf.sql and the SQL Server Management Studio will be launched.
3. Login to the SQL Server Management Studio.
4. Click the Execute button. This will run the script that creates the tables in the RadPdf
Database you created.
Figure 19 Executing radpdf.sql
5. When finished, close the SQL Server Management Studio.
27
3
CoSign Web App User Guide
Installing RAD PDF
1. Download the RAD PDF installer from the RAD website:
http://www.radpdf.com/install/
2. When queried, indicate you wish to install the ‘Complete’ package.
3. Run the installation. Before finishing the installation, make sure the Start PDF RAD
Service checkbox is checked.
Figure 20 Selecting to Start the RAD PDF Service
28
Using CoSign Web App for Signing and Validating Documents
3
4. If you want to change some RAD PDF Administration settings, such as when documents
will be deleted from the database, run the RAD PDF Administration tool. A shortcut to the
tool was added to your Start menu.
Figure 21 RAD PDF Administration Tool
Note that you must first provide the SQL Maintenance Connection String before you can
actually make any changes. For example: Integrated Security=SSPI;Persist Security
Info=False;Initial Catalog=RadPdf.
For instructions on how to create the string, refer to Creating the Maintenance Connection
String for the RadPdf Database.
Refer to Chapter 7: Configuring the CoSign Web App for additional configuration actions
related to working with PDF forms.
29
3
CoSign Web App User Guide
Creating the Maintenance Connection String for the RadPdf Database
Perform the following to create the string you need for changing RAD PDF admin settings.
1. Create a new empty text file.
2. Rename the extension, from txt to udl (Microsoft Data link file type).
3. Double click the UDL file. The following Data Link Properties window appears:
Figure 22 Data Link Properties – Connection Details
4. Perform the following in the Data Link Properties window:
a. Select the SQL Server from the list (usually, this is your computer name).
b. Select Use Windows NT Integrated security.
c. Select the RadPdf database.
30
Using CoSign Web App for Signing and Validating Documents
3
d. Click Test Connection. A success message similar to the following should appear:
Figure 23 Data Link Properties – Test Connection Results
e. Click OK.
f.
Click OK again to close the window.
5. Right click the UDL file and select Open with Notepad. The contents of the file should
be similar to the following:
Figure 24 UDL File Contents displaying the SQL Connection String
6. Locate the text after the Provider value. This text is the connection string. In the example
shown above it is:
Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=RadPdf;Data
Source=ERL2-PC
Note that the Data Source will appear only if the RAD PDF database is installed on
another PC. Otherwise, the connection string will be similar to the following:
Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=RadPdf
31
3
CoSign Web App User Guide
Uninstalling the CoSign Web App
To uninstall the CoSign Web App:
1. Open the Internet Information Services (IIS) Manager program that manages the
Microsoft Web Server.
2. In the connection pane, right-click the web site under Sites and click Remove.
3. Go to the location where the CoSign Web App files are located and delete that directory.
4. Uninstall the CoSign Client.
Note that because the CoSign Web App leaves no footprints of files or other elements such as
graphical images, you do not need to delete any temporary files as part of the uninstall
procedure.
32
Chapter 4: Using CoSign Web App for Signing and
Validating Documents
Using CoSign Web App, you can digitally sign and validate documents without having to
install any client software. The workflow is as follows:
1. Log into CoSign Web App.
2. Select a document.
3. View the document contents.
4. Sign empty signature fields and/or create signatures.
5. Validate existing signatures, if desired.
6. Save or send the signed copy.
Logging in to the CoSign Web App
In order to view documents, sign them and validate them, you must first login to the CoSign
Web App. Login is performed based on your CoSign user ID and password.
To login to CoSign Web App:
1. Access CoSign Web App by entering its URL, such as : https://cosignweb.org.com.
The CoSign Web App login page appears:
33
4
CoSign Web App User Guide
Figure 25 CoSign Web App Login Page
2. In the User name / Email field:
 Enter your User name if CoSign Web App is using a local CoSign appliance or
appliances.
 Enter your email address if CoSign Web App is using CoSign appliances deployed in
the Cloud.
3. Enter your password in the Password field.
4. Click Sign in.
The Select Document window appears (Figure 26).
Note that if you do not perform any action in CoSign Web App for a few minutes, you will be
automatically logged off.
Note that if CoSign Web App is installed and configured to use Kerberos Ticketing in an
Active Directory environment, or is setup to use an External Identity Provider, you will be
either already authenticated by the domain, or redirected to be authenticated by the External
Identity provider. In either case, the above login window will not appear.
34
Using CoSign Web App for Signing and Validating Documents
4
Selecting a Document
The window that appears immediately after logging in is the Select Document window.
Figure 26 Select Document Window
You can select a document in either of two ways:
 From your PC or device – Click Browse to select a local document. This option is not
available when using an iPad or iPhone.
 From the Cloud –Click to access one of the Cloud-based file storage services and select
your file. This method is especially useful for mobile devices (tablets and smartphones)
that do not have a local Browse functionality. For details, refer to Selecting a File from a
Cloud-Based File storage Service.
35
4
CoSign Web App User Guide
Selecting a File from a Cloud-Based File storage Service
1. In the Select Document window (Figure 26), select one of the following:
 Dropbox
 Google Drive
 Box
 Microsoft OneDrive
You are redirected to the Login window of the selected service.
2. Log into the service.
3. Optionally select the Remember me option if you want the browser to remember your
credentials.
4. The first time you access the Cloud-based file storage service from CoSign, right after
logging in to Dropbox you may be asked to confirm that you grant CoSign access to the
service.
Figure 27 Confirm CoSign Access to Dropbox
5. Allow access.
CoSign will save your login information so that you can automatically log into the service
without having to enter credentials each time
Also, depending on the Cloud-based file storage service, you will be notified by email that
the CoSign application would like to connect with your Dropbox account.
36
Using CoSign Web App for Signing and Validating Documents
4
Refer to Chapter 6 for a description of the end user experience when signing using a
Cloud-based file storage service.
Refer to Integrating with Cloud-Based File Storage Services for instructions on how to
register an organizational account for the various Cloud-based file storage providers.
Viewing and Signing Documents
After uploading a document to CoSign Web App, you can view all its pages, locate existing
signature fields (both signed and empty ones) and sign empty signature fields, as well as
create &amp; sign new signature fields.
Starting from CoSign Web App version 7.1, you can also upload Word and Excel
2007/2010/2013 documents, and produce Office 2007/2010/2013 signatures.
However, you cannot add new signatures to these documents, but only sign empty existing
signature fields or view the details of signed field.
The file you loaded appears in the CoSign Web App window.
 If the document does not contain any empty signature fields, by default it will appear with
a signature-creation frame hovering in the middle of the window. When you browse
through the pages, that frame will appear on every page. The frame enables you to create a
signature field on any page, position and resize it, and then sign inside it.
Figure 28 Example of a Loaded Document Without Empty Signature Fields
37
4
CoSign Web App User Guide
 If the document has pre-existing empty signature fields, by default it will appear without a
signature-creation frame. You will be able to sign the empty fields but will not able to
move or resize them.
Figure 29 Example of a Loaded Document With Empty Signature Fields
Note: Within CoSign Web App you cannot create an empty signature field. If you do
not sign inside a signature-creation frame, no field is created.
However, documents loaded into CoSign Web App can contain empty signature fields,
and you can sign those fields within CoSign Web App.
38
Using CoSign Web App for Signing and Validating Documents
4
Viewing Pages
Use the select-page carousel to browse through the document
The five page icons correspond to page numbers. Click the left arrow for the previous five
pages, or the right arrow for the next five pages. Blue arrows above and below a page icon
indicate the currently-displayed page.
If a PDF document has pre-existing empty signature fields, the select-page carousel indicates a
page containing empty signature fields using a sign icon instead of the page number.
.
Use the zoom icons to zoom in and out.
Note that for an Office 2007/2010/2013 document there is no indication which pages are
signed. Instead, general information about the document signatures is provided.
39
4
CoSign Web App User Guide
Using PDF forms
Starting from CoSign version 7.5, you can also view, fill-in and sign PDF forms in CoSign
Web App.
You can view the PDF form and fill-in the fields such as text boxes and option menus, as
shown in the example below.
Figure 30 Example of PDF Form Appearance in CoSign Web App
After clicking Continue, the filled-in document will be presented for the purpose of signing,
like a regular PDF file presented for signing.
40
Using CoSign Web App for Signing and Validating Documents
4
Signing a PDF Document
You can either sign a pre-existing empty signature field, or create a new field and sign it.
1. If you wish to sign a pre-existing field, skip to step ‎2. If you are creating a new signature
field, perform the following:
a. Locate the hovering signature-creation frame (see Figure 28). If the signature-creation
frame is not displayed, click
.
b. Optionally, move the frame to the desired location on the page, as follows:
 In a PC, click inside the frame and drag.
 In a mobile device, touch inside the frame and drag.
c. Optionally, resize the frame, as follows:
 In a PC, click a side or a corner and drag.
 In a mobile device, touch a side or a corner and drag.
2. Click/tap
in the signature frame. The Signature Appearance window appears.
Figure 31 Signature Appearance Window
41
4
CoSign Web App User Guide
3. Select a graphical signature from the carousel. Alternatively, click the radio button to Sign
without a graphical signature.
Note that a user’s graphical images and default settings are kept in the user's account in
the CoSign appliance.
4. Optionally, add a reason and title to the signature, and define your signature appearance.
To do so, click/tap Add reason and change signature appearance. The window
refreshes to display the following:
Figure 32 Adding Reason and Defining Appearance
5. In you created a new field, edit the appearance as desired by selecting whether to show the
date and time, the signer’s title, etc.
If you are signing a pre-existing field, you can only enter the reason and title if those are
required.
42
Using CoSign Web App for Signing and Validating Documents
6. Click/tap
4
.
The document will display a digital signature, similar to the following:
Figure 33 Sample Signature
7. You can optionally click the signature to view its details. Refer to Viewing Signature
Details.
Note that also PDF forms can be signed. The signature applies to the information entered by
the user in the form, in addition to the regular content.
Signing Office 2007/2010/2013 Documents
Using CoSign Web App, you can sign existing signature fields in Office documents. Note that
you cannot create new signature fields.
By default, if an Office document contains at least one signature or signature field, it is not
converted to PDF when you upload it into CoSign Web App and you can sign it in CoSign
Web App.
CoSign Web App supports the signing of signature fields that were created by the Microsoft
Signature Line provider or ARX Signature Line Provider. However, it is recommended to
create signature fields using the Microsoft Signature Line provider to avoid rendering
problems. If a signature field was created using the ARX Signature Line Provider, the text
“Software is required” appears in the location of the empty signature field.
To define whether an Office document containing signature fields is converted to PDF when it
is uploaded to CoSign Web App, refer to OfficeBackwardCompatibility.
Note: As described in the CoSign client guide, a user may sign a Word/Excel document
only if the certificate chain is trusted. That is, the CoSign ROOT certificate must be
trusted in the Web App platform. You can use the Install CoSign CA Certificate option of
the CoSign Configuration utility to instruct Web App to trust the CoSign ROOT
certificate.
43
4
CoSign Web App User Guide
To sign an Office document:
1. Optionally view the signature information appearing in the top right corner. In the
example shown below, the information is that the document contains three unsigned
signature fields.
2. Click/tap Sign Document.
If the document has more than one empty field, a list of the signature field identifiers
(taken from the Suggested Signer attribute of the signature fields) is displayed. Select a
signature field and click/tap Close.
44
Using CoSign Web App for Signing and Validating Documents
4
The Signature Appearance window appears.
3. Click/tap Add Reason and change signature appearance if you wish to add more
information to the signature, such as a reason.
4. Click/tap Apply. The document is signed.
The information in the upper right corner is updated.
45
4
CoSign Web App User Guide
Viewing Signature Details
You can view the signature details of each signature.
 In a PDF document, click any signature, whether pre-existing or created by you, to view
its details.
A Details window similar to the following is displayed.
Figure 34 Signature Details for a PDF Document
 For an Office 2007/2010/2013 document, a signature summary report appears in the top
right corner of the screen.
Click valid to view information about each signed field.
Figure 35 Signature Summary Report for an MS Office Document
A Signature Details window similar to the following is displayed.
46
Using CoSign Web App for Signing and Validating Documents
4
Figure 36 Signature Details for an MS Office Document
Validating Signatures
You can view the validity status of each signed signature field.
 In a PDF document:
Each signature displays in its top left corner an indication of the validity of the signature
(see Figure 33). A green checkmark indicates the signature is valid, and a red X indicates
it is invalid.
In addition, clicking/tapping a signature field displays the Signature Details window
(Figure 34), which lists the status of the signature and provides information about the user
certificate.
 In an Office 2007/2010/2013 document:
A signature summary report appears in the top right corner of the screen.
Click valid in the summary report to view information about each signed field, including
its validity status (see Figure 36).
47
4
CoSign Web App User Guide
Post-Signing Actions
When you finish viewing and signing the entire document, click/tap Done. The following
window appears.
Figure 37 What Would You Like to Do Next Window
You can select any of the following options:
 Save in &lt;file storage service&gt; – Save a signed copy of the file back in the Cloud-based
file storage service. The copy is a new file, and must be given a new name (you cannot
overwrite the original file). This option appears only if you retrieved the file from a
Cloud-based file storage service. The name of the option indicates the specific file storage
service from which you retrieved the file.
 Download copy – Download a signed copy to your computer’s Downloads folder. The
copy is a new file but its name is the name of the original file.
This option may not appear when using a mobile device (for example, on iPads).
 Send via email – Send the file as an attachment using your default mail application.
When you select this option, an email message frame appears within the window. You can
enter multiple recipients, separated by semicolons, in the To field. Enter any text in the
Subject field and main body of the email. Clicking/tapping Send will send the message
with the signed document added as an attachment.
Starting from CoSign Web App version 7.1, an auto-complete mechanism can be used to
assist in filling in previously-used email addresses.
48
Using CoSign Web App for Signing and Validating Documents
4
Figure 38 Sending the Signed File Via Email
 Close document – Closes the document and returns to the CoSign Web App home page.
This is equivalent to canceling the sign operation.
49
4
CoSign Web App User Guide
Signing in a Point of Sale Mode of Operation
You can set your account to work in a Point of Sale (POS) mode of operation. In this mode of
operation, each empty signature field can be signed electronically (intended for external
customers), or digitally (intended for the agent, a CoSign user). POS mode supports only PDF
files.
Once the document is digitally signed, it is not possible to add new electronic signatures
(customer signatures). Therefore make sure the document is first signed electronically
wherever needed before signing it digitally.
For instructions on how to set your account to work in a Point of Sale mode of operation, refer
to EnablePOSMode.
To sign in POS mode:
1. If you wish to sign a pre-existing field, skip to step ‎2. If you are creating a new signature
field, perform the following:
 Locate the hovering signature-creation frame (see Figure 28). If the signature-creation
frame is not displayed, click
.
2. Click/tap
in the signature frame. The POS Signing window appears.
Figure 39 POS Signing Window
50
Using CoSign Web App for Signing and Validating Documents
4
The page displays two tabs: Customer tab and Agent tab. Customers should use the
Customer tab, which creates an electronic signature, and the CoSign user should use the
Agent tab, which creates a digital signature.
By default the Customer tab is selected.
3. To create a Customer signature:
a. Instruct the customer to electronically sign in the signature area (typically using the
agent’s tablet or iPad).
b. Click/tap the Customer tab if you wish to add additional information to the electronic
signature.
Figure 40 POS Customer Signature Additional Fields
c. Optionally add a reason and title to the signature, and define the signature appearance.
d. Click/tap
.
51
4
CoSign Web App User Guide
4. To create an Agent signature:
a. Click the Agent tab. A Signature Appearance window appears.
Figure 41 POS Agent Signature Appearance Window
b. Select a graphical signature from the carousel. Alternatively, click the radio button to
Sign without a graphical signature.
Note that a user’s graphical images and default settings are kept in the user's account
in the CoSign appliance.
c. Optionally, add a reason and title to the signature, and define your signature
appearance. To do so, click/tap Add reason and change signature appearance. The
window refreshes to display the following:
52
Using CoSign Web App for Signing and Validating Documents
4
Figure 42 POS Agent - Adding Reason and Defining Appearance
d. In you created a new field, edit the appearance as desired by selecting whether to
show the date and time, the signer’s title, etc.
If you are signing a pre-existing field, you can only enter the reason and title if those
are required.
e. Click/tap
.
The document will display a digital signature, similar to the following:
Figure 43 Sample Signature
5. You can optionally click the signature to view its details. Refer to Viewing Signature
Details.
53
Chapter 5: Adding Graphical Signatures and Modifying
User Settings
Using CoSign Web App, you can add graphical signatures and modify various user settings
such as your signature appearance.
Adding Graphical Signatures
You can add personal graphical signatures using any of the following methods:
 Sketching
 Typing
 Uploading a graphic file
The graphical signatures you add are kept in your user account inside the CoSign appliance.
To add graphical signatures:
1. Open the drop-down list adjacent to your user name, in the top right corner of the CoSign
Web App window (Figure 44).
Figure 44 User Settings Drop-Down List
2. Select My Signatures.
54
Adding Graphical Signatures and Modifying User Settings
5
Figure 45 My Signatures – Adding New Graphical Signatures
3. Add a signature using any of the following methods:
 Sketch – Use the mouse in a desktop computer, or sketch with your finger upon a
mobile device. You can then save or cancel the sketch.
 Type – Select a font from among nine fonts and type in the desired text. You can then
save or cancel the signature.
 Upload – Upload a jpeg or bmp file.
55
5
CoSign Web App User Guide
Modifying User Settings
You can modify and update your user settings that affect the CoSign Web App session. All
these parameters are kept in your user account inside the CoSign appliance.
To modify user settings:
1. Open the drop-down menu adjacent to your user name, in the top right corner of the
CoSign Web App window (Figure 44).
2. Select Settings.
Figure 46 My Signatures
3. Optionally, set any of the following:
 Title – Enter a default title.
 Change Password – Change your password, if relevant (for example, if CoSign is
installed in a Directory Independent environment).
56
Adding Graphical Signatures and Modifying User Settings
5
 Default Signature Appearance – Specify the appearance of signature fields you will
be creating. Set the appearance by selecting or deselecting the following:

Show graphical signature

Show date and time
 Show my name

Show my title

Show signature reason
 Reasons for Signing – You can maintain a list of reasons that are displayed
whenever a reason needs to be added to a digital signature. You can add reasons to the
list and remove reasons from the list, edit existing reason and select a reason to be the
default reason.
 Advanced Settings – Define the following advanced settings, applying to all signature
fields you will be creating:
 Signature type – Defines whether the signature type will be Digital, Electronic, or
Invisible Digital.
 Date format – Defines the date format of the signatures.
 Time format – Defines the time format of the signatures.
 Display format – Defines whether only a date is displayed as part of the digital
signature, or both date and time are displayed.
 Operational Mode – Define whether CoSign Web App works in standard operation mode
or in Point of Sale mode:
 Standard – The regular mode of operation described in this guide.
 Point of Sale – A mode of operation where external users supply an electronic
signature while being overseen by an organizational representative, such as a Sales
representative, who digitally signs the overall transaction. For more information, refer
Signing in a Point of Sale Mode of Operation.
57
5
CoSign Web App User Guide
Logging off the CoSign Web App
Starting from CoSign Web App version 7.5, a user can log out of his/her session by
clicking the Log Off option.
Figure 47 Log Off the CoSign Web App
After selecting the Log Off option:
 When CoSign Web Agent is integrated with a Document Management system, the user is
directed back to the Document Management System.
 If an external Identity Provider is used, you can configure to which the web page the user
is redirected upon logoff. For information, refer to the description of LogoutRedirectURL.
In any case, whenever you logoff and an external Identity Provide is used, the external
Identity Provider is notified regarding the user logoff operation.
 In all other cases, the CoSign Web App Login page is displayed.
58
Chapter 6: Signing Documents from Cloud-based File
Storage Services
As mentioned above, the document that needs to be signed can be extracted from a Cloudbased file storage service, signed using the CoSign Web App, and then loaded back to the
Cloud-based file storage system or sent via email.
This chapter describes the end user experience for the following Cloud-based file storage
services: Dropbox, OneDrive, Google Drive, and Box.
In Box and Google Drive, you can sign with CoSign from within Box or Google Drive. That
is, after you select a certain document, you are redirected to CoSign Web App to digitally sign
the document, and after the document is signed, a signed copy is saved to either Box or
Google Drive.
Note that your organization needs to perform some integration tasks to register the CoSign
Web App as an application in the relevant Cloud-based file storage service. These integration
tasks are described in Integrating with Cloud-Based File Storage Services.
Signing Documents from Dropbox
When you first attempt in CoSign Web App to sign documents that are stored in Dropbox, you
are asked to confirm that you grant CoSign access to your data:
Figure 48 Confirm CoSign Access to Dropbox
After you click Allow, you will receive an email notifying you that the CoSign application will
interface your Dropbox account.
You can now proceed to view, sign and save the file in CoSign Web App.
59
6
CoSign Web App User Guide
Signing Documents from OneDrive
When you first attempt in CoSign Web App to sign documents that are stored in OneDrive,
you are asked to confirm that you grant CoSign access to your data:
Figure 49 Confirm CoSign Access to OneDrive
After you click Yes you can proceed to view, sign and save the file in CoSign Web App.
60
Signing Documents from Cloud-based File Storage Services
6
Signing Documents from Google Drive
When you first attempt in CoSign Web App to sign documents that are stored in Google
Drive, you are asked to confirm that you grant CoSign access to your data:
Figure 50 Confirm CoSign Access to Google Drive
After you click Allow Access you can proceed to view, sign and save the file in CoSign Web
App.
61
6
CoSign Web App User Guide
Invoking the Signature Operation from Within Google Drive
Every end-user can configure Google Drive so that he/she can invoke a digital signature
operation upon a selected document from within Google Drive.
In order to have CoSign appear in your Google Drive menus, you need to connect the CoSign
Digital Signatures application to Google Drive, as described in this section.
Note: As a prerequisite, a CoSign administrator must first configure the Google Drive
CoSign application, as described in Enabling Users to Sign from Within Google Drive.
To add CoSign to Google Drive Menus:
1. Click a file, select Open with and select Connect more apps.
2. Search for the CoSign Digital Signatures application.
The search results window appears:
Figure 51 Connecting the CoSign Application in Google Drive
3. Click + Connect. The following window appears:
Figure 52 CoSign Connected to Google Drive
62
Signing Documents from Cloud-based File Storage Services
6
4. Select whether to make CoSign Digital Signatures application the default application for
files it can open.
5. Click OK.
6. Restart your browser.
The CoSign Digital Signatures application now appears in the Open with menu of every PDF,
Word or Excel file you select in Google Drive, as shown in Figure 53:
Figure 53 Opening CoSign from Within Google Drive
Selecting CoSign Digital Signature redirects you to CoSign Web App with the selected file
appearing in the window. After finishing the signature ceremony, the updated signed
document is written back to the Google Drive storage. You can select whether the updated
signed file overwrites the original file or is saved as a new file.
63
6
CoSign Web App User Guide
Signing Documents from Box
When you first attempt in CoSign Web App to sign documents that are stored in Box, right
after logging in to Box you are asked to confirm that you grant CoSign access to your data:
Figure 54 Confirm CoSign Access to Box
After you authorize access you can proceed to view, sign and save the file in CoSign Web
App.
64
Signing Documents from Cloud-based File Storage Services
6
Invoking the Signature Operation from Within Box
Every end-user can configure Box so that he/she can invoke a digital signature operation upon
a selected document from within Box.
In order to have CoSign appear in your Box menus, you need to add the CoSign Digital
Signatures application to your apps, as described in this section.
Note: As a prerequisite, a CoSign administrator must first configure the Box CoSign
application, as described in Enabling Users to Sign from Within Box.
To add CoSign to Box Menus:
1. Go to your Apps section.
Figure 55 Box Apps Section
2. Search for the CoSign Digital Signatures application.
The search results window appears:
Figure 56 Searching for the CoSign App in Box
3. Click the CoSign icon. The following window appears.
65
6
CoSign Web App User Guide
Figure 57 Adding the CoSign App to Box
4. Click + Add.
The CoSign Digital Signatures application now appears in the right-click menu and More
Actions menu of every file you select in Box, as show in Figure 58.
Figure 58 Opening CoSign from Within Box
Selecting Digitally Sign with CoSign redirects you to CoSign Web App with the selected file
appearing in the window. After finishing the signature ceremony, the updated signed
document is written back to the Box storage. You can select whether the updated signed file
overrides the original file or is saved as a new file.
66
Chapter 7: Configuring the CoSign Web App
This chapter describes the CoSign Web App customizations that a CoSign admin can perform.
These include:
 Modifying various CoSign Web App parameters. All CoSign Web App related
configuration is performed in the web.config file, located in the home directory of the
CoSign Web App application.
 Configuring CoSign Web App in passive ADFS mode. This is a prerequisite for service
providers who wish to offer digital signature services to organizations that deploy Active
Directory with ADFS.
 Registering the CoSign Web App as an application in the various Cloud-based file storage
services. This is a prerequisite if you wish to use CoSign Web App to sign files stored in a
Cloud-based file storage system.
Modifying CoSign Web App Parameters
You can modify various CoSign Web App parameters by editing the web.config file, located
in the home directory of the CoSign Web App application.
Important: Because the web.config file contains all the CoSign Web App definitions,
it is recommended to back up the file before making any changes to it.
Modifying Image Setting Parameters
The default Image Settings configuration is as follows:
&lt;ImageSettings&gt;
&lt;!-- add here Image settings--&gt;
&lt;add key=&quot;ReducePercent&quot; value=&quot;100&quot;/&gt;
&lt;add key=&quot;ReduceIterations&quot; value=&quot;1&quot;/&gt;
&lt;/ImageSettings&gt;
The ReducePercent and ReduceIteration parameters provide the instructions for shrinking
an uploaded graphical signature image if its size is larger than 30K. ReducePercent specifies
by how much to shrink the image at each iteration. ReduceIteration specifies the maximum
number of iterations.
67
7
CoSign Web App User Guide
Defining SMTP Settings
The SMTP Settings section is by default empty.
&lt;SMTPSettings&gt;
&lt;!-- add here SMTP settings--&gt;
&lt;/SMTPSettings &gt;
You can enter the following parameters into the section. If the parameters already appear in
your web.config file, you can changes their values as needed.
 To set the SMTP host IP/Name:
&lt;add key=&quot;SMTPHost&quot; value=&quot;THE_VALUE&quot; /&gt;
 To set the SMTP Port:
&lt;add key=&quot;SMTPPort&quot; value=&quot;THE_VALUE&quot; /&gt;
 To set the sender address:
&lt;add key=&quot;SMTPMailFrom&quot; value=&quot;THE_VALUE&quot; /&gt;
 To set the mail message body:
&lt;add key=&quot;SMTPMessageBody&quot; value=&quot;THE_VALUE&quot; /&gt;
 To set the mail Subject:
&lt;add key=&quot;SMTPMailSubject&quot; value=&quot;THE_VALUE&quot; /&gt;
Defining Extended Authentication Settings
The Extended Authentication Settings section is empty by default.
&lt; ExtAuthSettings&gt;
&lt;!-- add here extended authentication settings--&gt;
&lt;/ ExtAuthSettings&gt;
If CoSign is configured to use extended authentication, configure extended authentication
parameters in the ExtAuthSettings section.
68
Configuring the CoSign Web App
7
 To force Prompt for sign:
&lt;add key=&quot;PromptForSign&quot; value=&quot;Never/Always&quot; /&gt;
 Never – The user will not be requested to provide a password for every digital
signature operation. This is the default behavior.
 Always – The user will be required to enter his/her password for every signature
operation (as illustrated in Figure 59).
Figure 59 Example of Password Requested Upon Every Signature Operation
 To force extended password usage:
&lt;add key=&quot;ExtPwdRequired&quot; value=&quot;Yes/No&quot; /&gt;
 No – No extended authentication mechanism is used. This is the default value.
 Yes – An extended authentication mechanism is used, such an OTP (One Time
Password) device. Figure 60 provides an example of this scenario.
In this case, you must make sure that the CoSign appliance is configured to use
extended authentication.
69
7
CoSign Web App User Guide
Figure 60 Extended Authentication Required
70
Configuring the CoSign Web App
7
Defining API Integration Settings
By default, the API Settings section is empty. This section enables applications to redirect
users to the CoSign Web App for the purpose of signing documents during their session with
the application.
&lt; APISettings&gt;
&lt;!-- add here API integration settings--&gt;
&lt;/ APISettings&gt;
The following configuration parameters can be defined (for more information, refer to section
VI of the CoSign Programmer Guide).
 To enable API request handling:
&lt;add key=&quot;EnableAPIRequests&quot; value=&quot;true/false&quot; /&gt;
 false means that no application can interact with the CoSign Web App. This is the
default setting.
 true means that an application can redirect their users to communicate with the
CoSign Web App for the purpose of signing documents.
 To enable Google Drive integration (default=true)
&lt;add key=&quot;EnableGoogleDriveIntegration&quot; value=&quot;true/false&quot; /&gt;
For more information, refer to Enabling Users to Sign from Within Google Drive.
 To enable Box integration (default=true)
&lt;add key=&quot;EnableBoxIntegration&quot; value=&quot;true/false&quot; /&gt;
For more information, refer to Enabling Users to Sign from Within Box.
 To define an API request session timeout (default=30 min.)
&lt;add key=&quot;APIRequestTimeOut&quot; value=&quot;30&quot; /&gt;
If the application does not collect back the signed document after this timeout, the
document will be erased from the memory of the CoSign Web App.
Defining General Settings
The following general settings can be set in the General Settings section.
 The following parameters specify whether a link exists for the Forgot My Password
functionality, as well as its name and URL:
 To activate a &quot;Forgot my password&quot; link:
&lt;add key=&quot;ForgetPwdVisible&quot; value=&quot;true/false&quot; /&gt;
 To set the &quot;Forget my password&quot; link text:
&lt;add key=&quot;ForgetPwdText&quot; value=&quot;THE_VALUE&quot; /&gt;
71
7
CoSign Web App User Guide
 To set the &quot;Forget my password&quot; link URL:
&lt;add key=&quot;ForgetPwdUrl&quot; value=&quot;THE_VALUE&quot; /&gt;
 The following parameters specify whether a link exists for the Sign Up functionality, as
well as its name and URL:
 To activate a &quot;Sign up&quot; link:
&lt;add key=&quot;SignUpVisible&quot; value=&quot;true/false&quot; /&gt;
 To set the &quot;Sign up&quot; link text:
&lt;add key=&quot;SignUpText&quot; value=&quot;THE_VALUE&quot; /&gt;
 To set the &quot; Sign up &quot; link URL:
&lt;add key=&quot;SignUpUrl&quot; value=&quot;THE_VALUE&quot; /&gt;
 The following additional parameters can be setup:
 To enable or disable the change password functionality:
&lt;add key=&quot;EnableChangePwd&quot; value=&quot;true/false&quot; /&gt;
Note: In Directory Independent installations, the change password option is enabled by
default.
 To set the default domain name (default value = &quot;&quot;)
&lt;add key=&quot;DefaultDomain&quot; value=&quot;arx&quot; /&gt;
This parameter is relevant in cases where CoSign is installed in an Active Directory
environment. If the default domain name is specified using DefaultDomain, the user
will not be required to supply the CoSign Domain Name.
 To enable working with AD (default value = &quot;false&quot;)
&lt;add key=&quot;ADMode&quot; value=&quot;true/false&quot; /&gt;
This parameter is relevant in cases where CoSign is installed in an Active Directory
environment. If the CoSign Client is configured to use CoSign in an Active Directory
environment, the CoSign Web App will work even without setting ADMode to true.
However, if the ADMode parameter is set to true, the GUI of the CoSign Web App
will be slightly changed, for example, the user settings will not include the change
password option.
 The following additional parameters are relevant for CoSign Web App V7.1 and above:
 To enable or disable the Point of Sale (POS) functionality globally for all users:
&lt;add key=&quot;EnablePOSMode&quot; value=&quot;true/false&quot; /&gt;
The default value is false, meaning POS mode is not globally enabled. To enable
POS mode for an individual user, refer to Operational Mode in the Modifying User
Settings section.
When the value is true, all users have the capability to execute a POS signature
process.
72
Configuring the CoSign Web App
7
 To enable or disable the new Office capability, in which Office 2007/2010/2013
documents are not converted to PDF if they contain one or more signature fields:
&lt;add key=&quot;OfficeBackwardCompatibility&quot; value=&quot;true/false&quot; /&gt;
The default value is false which instructs the system not to convert Word and Excel
2007/2010/2013 documents to PDF if they contain one or more signature fields.
 The following additional parameters are relevant for CoSign Web App V7.5 and above:
 As part of the functionality of CoSign Client/CoSign Signature APIs version 7.5, it is
possible to handle Signature Locators as signature fields (for more information about
Signature Locators, refer to the CoSign Signature APIs Developer’s Guide). If you
enable this option, the CoSign Web App will show Signature Locators as signature
fields.
To enable or disable the new functionality use the following parameter:
&lt;add key=&quot;Enable Locators&quot; value=&quot;true/false&quot; /&gt;
The default value is false, which instructs the system not to handle Signature
locators.
 As part of the functionality of CoSign Client/ CoSign Signature APIs version 7.5, it is
possible to redirect the user to a specific Logoff URL if either an External Identity
Provider is used or the Active Directory Kerberos Ticketing mechanism is used.
To do so, use the following parameter:
&lt;add key=&quot;LogoutRedirectURL&quot; value=&quot;&lt;URL&gt;&quot; /&gt;
If a URL value is supplied, the user will be redirected to that URL upon clicking the
Log Off option.
Configuring CoSign Web App in Passive ADFS Mode – Using the
WS Federation Protocol
CoSign Web App can be deployed by a service provider to offer individuals and organizations
digital signature services. Any end user who wishes to use the service must be added to the
service either manually or automatically through CoSign APIs. The end user is authenticated
to the service using a User ID and password mechanism.
The service provider can offer digital signature services to organizations that deploy Active
Directory with ADFS. By configuring a trust between the service provider and the
organization that wishes to use the services, any user that belongs to the organization can
communicate automatically using the ADFS ticketing mechanisms (based on the SAML
standard).
Using the ADFS ticketing mechanism, the end user first uses the local Active Directory
services to authenticate and receive an ADFS ticket. The ADFS ticket is then used as a
mechanism to connect to CoSign Web App, with the initial communication creating a new
account for the user (including a digital signature key and a certificate). The end user can then
continue using the account to sign documents.
73
7
CoSign Web App User Guide
This section describes how a digital signature service provider should configure CoSign Web
App to enable users of an organization that deployed ADFS to use the CoSign Signature
service. The description is based on using ADFS with the WS Federation protocol.
The following configuration is required for every organization that wishes to use the Web App
service. It consists of two tasks:
 Configuring Web App for ADFS with WS Federation Protocol
 Running the Microsoft Federation Utility
For more information about the ADFS functionality provided by the CoSign appliance, refer
to the ADFS sections in the CoSign Administrator Guide.
Note: Alternatively, you can use the SAML2 protocol to enable users to use the CoSign
Signature service . This is discussed in Configuring CoSign Web App in SAML2
Protocol Mode.
Configuring Web App for ADFS with WS Federation Protocol
1. Rename web.config.adfs to be web.config, thus overwriting the original
web.config file.
2. In the web.config file, add a line in the ADFSSettings section for every organization
you wish to trust, as follows:
&lt;ADFSSettings&gt;
&lt;add key=&quot;org1-ID&quot; value=&quot;https://adfs.org1.com/adfs/ls/&quot; /&gt;
&lt;add key=&quot;org2-ID&quot; value=&quot;https://adfs.org2.com/adfs/ls/&quot; /&gt;
&lt;/ADFSSettings&gt;
Where:
 key is the identification of an organization.
 value is the External Identity Provider URI for the ADFS service of this originating
organization.
 The URL for users wishing to connect to the Web App Service must be of the
following type:
https://&lt;web app DNS&gt;/org/&lt;identification of the originating organization&gt;, where
the &lt;identification of the originating organization&gt; has the same value as the key in
the web.config file.
For example:
https://webapp.service.com/org/Company-Z.
As part of CoSign v7.5 an additional parameter can be used:
 If you are using a Default Identity Provider, you can set a default redirect URL to the
identity provider as follows:
&lt;add key=&quot;ADFSDefualtRedirect&quot; value=&quot;&lt;URL&gt;&quot;/&gt;
74
7
Configuring the CoSign Web App
Running the Microsoft Federation Utility
The administrator deploying CoSign Web App must run the Fedutil utility for every new
organization wishing to use the digital signature service through ADFS.
1. Enable the Fedutil mechanism as follows:
 If the PC hosting CoSign Web App is running Windows 2008, install the package
from http://www.microsoft.com/en-us/download/details.aspx?id=17331.
 If the PC hosting the CoSign Web App is running Windows 2012, you need only
select the Windows Identity Foundation option in the Control Panel’s Turn
Windows features on or off section.
2. In the Microsoft IIS server on which CoSign Web App is installed, go to C:\Program
Files (x86)\Windows Identity Foundation SDK\v4.0 and execute fedutil.exe.
The Federation Utility Wizard welcome page appears.
Figure 61 Federation Utility – Welcome Page
3. In the Welcome page do the following:
a. In Application configuration location, specify the path to the web.config file for
your CoSign Web App website. For example:
C:\inetpub\CoSignWebApp\web.config.
b. In Application URI, specify the URI for your website. For example:
https://webapp.service.com/.
75
7
CoSign Web App User Guide
c. Click Next. The Security Token Service page appears.
Figure 62 Federation Utility – Security Token Service Page
4. In the Security Token Service page:
a. Select Use an existing STS.
b. Specify the FederationMetadata.xml file that was provided to you by the originating
organization that deployed the local ADFS deployment.
c. Click Next. The Security Token Encryption page appears.
76
Configuring the CoSign Web App
7
Figure 63 Federation Utility – Security Token Encryption Page
5. In the Security Token Encryption Page:
a. Select No encryption.
b. Click Next. The Offered Claims page appears.
77
7
CoSign Web App User Guide
Figure 64 Federation Utility – Offered Claims Page
6. The Offered Claims page displays information related to Claims that are defined in the
local ADFS of the originating organization. Review the claims and click Next.
The Summary page appears.
78
Configuring the CoSign Web App
7
Figure 65 Federation Utility – Summary Page
7. In the Summary page click Finish.
The Web App’s web.config file is updated, and information is created under the
FederationMetaData directory (the created file in the FederationMetaData
directory is the same for all customers).
8. Backup both the web.config file and the FederationMetaData directory.
9. The FederationMetaData directory contains the 2007-06\ FederationMetadata.xml
file. You may need to send the file to your end customer to be used as part of the Trusted
Relaying Party configuration in the customer’s ADFS server.
79
7
CoSign Web App User Guide
Configuring CoSign Web App in SAML2 Protocol Mode
As discussed in the previous section, CoSign Web App can enable users to login based on an
External Identity Provider. Various Identity Provider solutions use the SAML2 protocol
mechanism instead of WS Federation for managing all information required to enable SAML
based user authentication. CoSign ADFS can optionally be configured to use SAML2 protocol
instead of WS Federation.
Configuring CoSign ADFS to use the SAML2 protocol
1. In the web.config file, set the following in the General Settings section:
&lt;add key=&quot;ADFSMode&quot; value=&quot;true&quot;/&gt;
&lt;add key =&quot;SAML2Mode&quot; value=&quot;true&quot;/&gt;
 If you are using a Default Identity Provider, set a default redirect URL to the identity
provider as follows:
&lt;add key=&quot;ADFSDefualtRedirect&quot; value=&quot;&lt;URL&gt;&quot;/&gt;
Running the Saml2ConfigUtility
Additional configuration is required in order to establish SAML2 protocol based access to
CoSign Web App. Because there are various possible External Identity Providers, the
following description is written as generically as possible.
1. Create a folder named MetadataDocs under the WebApp folder (for example:
C:\inetpub\CoSignWeb\MetadataDocs).
2. Make sure the MetadataDocs directory may be accessed by the user account that
executes the Web App Web Server.
3. Locate the Saml2ConfigUtility in the CoSignWeb\bin directory.
4. Execute the saml2configutility.exe utility as follows:
saml2configutility.exe –cf &lt;config file name&gt; -op &lt;operation&gt;
[options]
Where
 config file name is the full path name to CoSign Web App’s web.config file.
 operation is one of the following operations:
 1 – Add WebApp configuration information as a Service Provider, to Web App’s .
web.config file. This operation should be executed first (before either
operation 3 or operation 2 is executed)
 2 – Import External Identity Provider information. Information will be imported
from the Meta Data file provided by the Identity Provider. This information will
be used to build a trust between the Identity Provider and CoSign.
80
Configuring the CoSign Web App
7
 3 – Export Web App information (as a Service Provider) to a Meta Data file that
will be sent to the Identity Provider. This Meta Data file will be used by the
Identity Provider to build trust between the identity Provider and CoSign.
 options depend on the type of operation, as described in:
 The saml2configutility.exe Options related to operation = 1
 The saml2configutility.exe Options related to operation = 2
 The saml2configutility.exe Options related to operation = 3
The saml2configutility.exe Options related to operation = 1
 [-a &lt;allowed audience URI&gt;] – Supply the URI of the Service Provider. If the
default Web App is used, then supply the URL of the CoSign Web App (for example
https://webapp.arx.com).
This parameter is mandatory.
 [-sig &lt;signing certificate thumbprint&gt;] – Enter the certificate thumbprint of
the CoSign Web App services’ SSL certificate (refer to step (‎4)(‎g) in Installing the
CoSign Web App Component).
This parameter is mandatory.
In the case of a certificate thumbprint, the specific account needs to have permission to
access the certificate and its key located inside the Microsoft certificate store.
The saml2configutility.exe Options related to operation = 2
 [-m &lt;Identity Providers Meta Data Path&gt;] – Enter the path for the Meta Data
files directory (for example C:\inetpub\CoSignWeb\MetadataDocs).
This parameter is mandatory. Use it only for adding the first IDP.
 [-id &lt;Identity Provider identification&gt;] – The identification for the Identity
provider. (for example http://fsweb.contoso.com/adfs/services/trust). This parameter
represents the ID of the federation partner to which this configuration pertains. This ID
must have a match in one of the metadata files that are known by the service provider
(entityID according to the SAML2 standard).
This parameter is mandatory.
 [-n &lt;Identity Provider Name&gt;] – The unique identification for the Identity
Provider. Use the DNS representation for the Identity provider.
This parameter is optional.
 [-sou &lt;Identity Provider Sign-On EndPoint URL&gt;] – The URL end Point for
the Identity Provider that will be accessed by the end user.
This parameter is optional. You can use this parameter to define a default URL different
from the one defined in the Metadata file.
 [-sob &lt;Identity Provider Sign-On EndPoint Binding&gt;] – The binding of the
end point of the Identity Provider to be accessed by the end user. Use the value post if
81
7
CoSign Web App User Guide
the EndPoint is accessed via an HTTP Post command, or redirect if the EndPoint is
accessed via a redirect command.
This parameter is optional. You can use this parameter to define a default value different
from the one defined in the Metadata file.
 [-slu &lt;Identity Provider Logout EndPoint URL&gt;] – The URL end Point for
the Identity Provider that will be accessed by the end user for the Logout operation.
This parameter is optional. You can use this parameter to define a default value different
from the one defined in the Metadata file.
 [-slb &lt;Identity Provider Logout EndPoint Binding&gt;] – The binding of the
end point of the Identity Provider to be accessed by the end user for the logoff operation.
Use the value post if the EndPoint is accessed via an HTTP Post command or redirect
if the EndPoint is accessed via a redirect command.
This parameter is optional. You can use this parameter to define a default value different
from the one defined in the Metadata file.
The saml2configutility.exe Options related to operation = 3
 -mf &lt;metadata.xml path&gt; – The file path for the Meta Data file that was prepared by
the Identity Provider for CoSign Web App. This file must be placed in the
C:\inetpub\CoSignWeb directory.
This parameter is mandatory.
 [-s] – Sign the Metadata file if the IDP requires to do so.
The following parameters are related to the contact person or division that provides the Web
App service (the SP).
 [-cn &lt;Contact Name&gt;] – The first name of the contact person running the Web App
Services.
 [-cs &lt;Contact Surname&gt;] – The surname of the contact person running the Web App
Services.

[-cc &lt;Contact Company&gt;] – The company name of the company running the Web
App Services.

[-ce &lt;Contact Email&gt;] – The email of the contact person running the Web App
Services..
 [-cp &lt;Contact Phone&gt;] – The phone number of the contact person running the Web
App Services.
 [-ct &lt;Contact Type&gt;] – The contact type of the contact person running the Web App
Services.
82
Configuring the CoSign Web App
7
Note that some External Identity Providers use a different method of interaction with the
Service Provider (in this case, the CoSign Web App). In this mode, the user communicates
directly with the SP via a SAML token provided by the IDP.
In this case, you will need to directly edit the web.config file and set the
allowUnsolicitedResponses as in the following example:
&lt;saml2&gt;
&lt;identityProviders metadata=&quot;METADATALOCATION&quot;&gt;
&lt;add id=&quot;IdProvider&quot; allowUnsolicitedResponse=”true”&gt;
&lt;endpoints&gt;
&lt;endpoint type=&quot;SignOn&quot; url=&quot;http://www.example.com/signon&quot; binding=&quot;POST&quot; /&gt;
&lt;endpoint type=&quot;Logout&quot; url=&quot;http://www.example.com/logout&quot; binding=&quot;POST&quot; /&gt;
&lt;/endpoints&gt;
&lt;/add&gt;
&lt;/identityProviders&gt;
&lt;/saml2&gt;
Configuration at the Identity Provider System
The Meta Data file of the Identity Provider must be generated and sent to the CoSign Web
App administrators, while the Meta Data file that represents the CoSign Web App as a Service
Provider must be imported to the Identity Provider system.
Please use the Identity Provider documentation to perform these tasks.
Note that browser related caching problem may occur when the user perform a logoff
operation. In such cases, even though the user performed a logoff operation, the user is
immediately logged on again due to the browser reusing cached information.
Please consult with the Identity Provider’s Web Services documentation to solve this problem.
For example, if the identity Provider deployment is based on IIS, you can consult the
following link: http://social.technet.microsoft.com/wiki/contents/articles/1600.ad-fs-2-0-howto-change-the-local-authentication-type.aspx.
83
7
CoSign Web App User Guide
Configuring CoSign Web App to use Microsoft Active Directory
Kerberos authentication
To enable using Active Directory Kerberos authentication, some required configurations need
to be performed. Some of the configurations are required in the Active Directory domain and
some are required on the Microsoft IIS deployment of the CoSign Web App.
Setting Web App’s web.config File
1. Modify the web.config file of the CoSign Web App as follows:
a. In the Configuration &gt; System.web section, change the authentication settings
from Forms to Windows.
b. In the same section, add an authorization sub-section in order to disable
anonymous access.
&lt;authentication mode=&quot;Windows&quot;&gt;
&lt;forms loginUrl=&quot;~/&quot; timeout=&quot;10&quot;/&gt;
&lt;/authentication&gt;
&lt;authorization&gt;
&lt;deny users=&quot;?&quot;/&gt;
&lt;/authorization&gt;
2. If the CoSign Web Agent is used together with the Active Directory Kerberos ticket
mechanism, you will need to enable Anonymous communication for the communication
between the Document management system and CoSign Web Agent. To do so, add the
following under the &lt;/authentication&gt; line shown in the preceding step.
&lt;anonymousIdentification enabled=&quot;true&quot; /&gt;
Using the setspn utility to establish a Kerberos based authentication scheme
To enable end-users to connect to the CoSign Web App using an Active Directory based
Kerberos mechanism, the Microsoft setspn command line utility can be used.
You can view more information related to the utility in https://technet.microsoft.com/enus/library/cc731241.aspx.
The utility defines Service Principle Name (SPNs) for a certain computer in the Active
Directory.
The utility can be executed in any PC which is not the Active Directory domain PC, using a
Domain Admin account.
84
Configuring the CoSign Web App
7
For example, if the PC that runs the CoSign Web App is named CoSign-Web-App-PC and
the domain is named Domain.arx.com, the PC should have the following SPNs:
HOST/CoSign-Web-App-PC
HOST/CoSign-Web-App-PC. Domain.arx.com
HTTP/CoSign-Web-App-PC
HTTP/CoSign-Web-App-PC. Domain.arx.com
RestrictedKrbHost/CoSign-Web-App-PC
RestrictedKrbHost/CoSign-Web-App-PC. Domain.arx.com
1. Run the utility with the –L flag as follows, to view the current SPN listing of the Web App
PC:
setspn –L &lt;web server name&gt;
In our example, run: setspn –L CoSign-Web-App-PC
2. To add missing SPNs, run the utility as follows for every missing item:
setspn –s &lt;SPN value&gt; &lt;Server name&gt;
For example, to set the HTTP/CoSign-Web-App-PC SPN for the CoSign-Web-App-PC
server, run:
setspn –s http/CoSign-Web-App-PC CoSign-Web-App-PC
3. Finally, it is recommended to run setspn –L &lt;web server name&gt; again to make sure
that all SPNs are listed.
Using Internet Explorer to Access CoSign Web App Based on Kerberos Ticketing
Organizations that want their end users to access the CoSign Web App using the Kerberos
ticketing mechanism should configure the following settings in the end user’s PC:
1. In Internet Options &gt; Advanced, check Enable Integrated Windows Authentication.
2. In Internet Options &gt; Security, add the Web App site to the trusted sites in Internet
Explorer.
3. In Internet Options &gt; Security, select the Internet zone and click Custom level…
Scroll to the bottom and check the option: Automatically logon with current user name
and password.
It is advisable to connect using the full DNS name of the CoSign Web App and not only with
the PC in the Intranet.
Note: the CoSign Web App PC should have a valid DNS name under the domain of the
organization, and also should be accessed via Internet Explorer using this DNS name.
85
7
CoSign Web App User Guide
Using Google Chrome to access CoSign Web App based on Kerberos Ticketing
The end user’s Registry entry should be defined with the following settings.
1. Add the following registry keys:
[HKEY_LOCAL_MACHINE\Software\Policies\Google\Chrome]
&quot;AuthNegotiateDelegateWhitelist&quot;=&quot;Error! Hyperlink reference not
valid.
&quot;AuthSchemes&quot;=&quot;basic,digest,ntlm,negotiate&quot;
&quot;AuthServerWhitelist&quot;=&quot;Error! Hyperlink reference not valid.
Configuring CoSign Web App to Work with PDF Forms
If you want the CoSign Web App to work with PDF forms, make the following changes in the
web.config file:
1. Under appSettings, set the RAD PDF license key. For example:
&lt;add key=&quot;RadPdfLicenseKey&quot; value=&quot;DEMO&quot;/&gt;
In a non-demo environment, enter the license key provided by RAD PDF (a base64
encoded string).
2. Under appSettings, set your SQL connection string. For example:
&lt;add key=&quot;RadPdfConnectionString&quot; value=&quot;Integrated
Security=SSPI;Persist Security Info=False;Initial
Catalog=RadPdf&quot;/&gt;.
Or, if the RAD PDF database is installed on another PC:
&lt;add key=&quot;RadPdfConnectionString&quot; value=&quot;Integrated
Security=SSPI;Persist Security Info=False;Initial
Catalog=RadPdf;Data Source=ANOTHER-PC”/&gt;
3. Under GeneralSettings , enable FormFill mode as follows:
&lt;add key=&quot;FormFillMode&quot; value=&quot;1&quot;/&gt;
Note that the possible values are:
0 – Disable FormFill mode
1 – Enable FormFill mode
2 – Automatic mode: Display files in FormFill mode only when there are fields to
fill.
86
Configuring the CoSign Web App
7
Integrating with Cloud-Based File Storage Services
The setup described in this section must be performed to enable users of your organization to
access documents stored in Cloud-based storage services such as Google Drive or Dropbox.
The following setup tasks must be performed:
 The CloudStorageSettings section of the web.config file must be updated to include
information regarding the Cloud-based storage services. For information, refer to Defining
Cloud Storage Settings.
 A dedicated application must be defined for the selected Cloud-based storage service. This
application will enable the CoSign Web App to access the user account in the Cloudbased storage services.
In the case of Google Drive or Box, you can configure these applications to enable
invoking Cosign from Google Drive or Box menus.
For information, refer to Creating an Application for Enabling Access to User Accounts in
the Cloud.
Note: Many Cloud Storage providers, such as Box, mandate using HTTPS protocol
for accessing the CoSign Web. It is highly recommended to do so.
Defining Cloud Storage Settings
The Cloud Storage Settings section is by default empty.
&lt; CloudStorageSettings &gt;
&lt;!-- add here Cloud Storage settings--&gt;
&lt;/CloudStorageSettings&gt;
The following configuration parameter must be set if you wish to integrate with any
Cloud-based storage systems:
 Enable using Dropbox as a Cloud-Based File Storage
&lt;add key=&quot;EnableDropbox&quot; value=&quot;true/false&quot; /&gt;
The default is enabled.
 Enable using Box as a Cloud-Based File Storage
&lt;add key=&quot;EnableBox&quot; value=&quot; true/false &quot; /&gt;
The default is enabled.
 Enable using OneDrive as a Cloud-Based File Storage
&lt;add key=&quot;EnableSkyDrive&quot; value=&quot; true/false &quot; /&gt;
The default is enabled.
Note: The internal naming convention for OneDrive is SkyDrive because SkyDrive
was the former name of this Storage Cloud Service.
87
7
CoSign Web App User Guide
 Enable using Google as a Cloud-Based File Storage
&lt;add key=&quot;EnableGoogle&quot; value=&quot; true/false &quot; /&gt;
The default is enabled.
Note that if a single cloud-based file storage is enabled, then only the icon for this cloud
storage will appear immediately after the user logs on. If no cloud-based file storage is
enabled, no indication of a cloud based file storage system appears.
 Set the Cloud storage callback URL (redirect URL):
&lt;add key=&quot;CloudStorageCallbackURL&quot; value=&quot;THE_VALUE&quot; /&gt;
When the user is redirected to the Cloud-based storage service for a login operation, the
Cloud-based storage system is redirected back to CloudStorageCallbackURL to continue
the user session in the CoSign Web App.
Specify the following value:
https://sign.xxx.com/cloudstorage/loggedtocloudstorage
where sign.xxx.com is the location where the CoSign Web App is deployed.
Creating an Application for Enabling Access to User Accounts in the Cloud
This section describes, for each type of Cloud-based storage service, how to create an
application enabling the CoSign Web App to access the user account in the Cloud-based
storage service.
Creating a CoSign Application in Dropbox
1. Connect to the Dropbox development portal at https://www.dropbox.com/developers and
login with a user account.
2. Select Apps Console.
3. Click Create app to create a new application.
88
Configuring the CoSign Web App
7
Figure 66 Creating a Dropbox API Application
4. Select the Dropbox API app option.
5. Select the following options:
a. What types of data does your app need to store on DropBox? – Select Files and
Datastores.
b. ”Can your app be limited to its own folder? – Select No.
c. What type of files does your app need access to? – Select All File Types.
d. Provide an app name, and you’re on your way – The recommended app name is
&lt;your organization name &gt; - CoSign.
6. Click Create app. The following form appears:
89
7
CoSign Web App User Guide
Figure 67 Dropbox API Application Forms
7. In the Application forms, supply additional information such as a description and icons.
After applying for production – there is no limit on the number of users who
can use the CoSign application.
8. Record the App key and App secret values for entering in the web.config file.
9. Click Update.
10. Enter the App key and App secret values in the DropBoxSettings section of the
web.config file. The DropBoxSettings section is by default empty.
&lt;DropBoxSettings&gt;
&lt;!-- add here DropBox settings--&gt;
&lt;/DropBoxSettings&gt;
a. Enter the DropBox App key value:
&lt;add key=&quot;AppKey&quot; value=&quot;THE_VALUE&quot; /&gt;
b. Enter the DropBox App Secret value:
&lt;add key=&quot;AppSecret&quot; value=&quot;THE_VALUE&quot; /&gt;
11. Click Apply for production.
It takes about a day for Dropbox to approve your CoSign app.
90
7
Configuring the CoSign Web App
Creating a CoSign Application in OneDrive
1. Connect to the OneDrive development portal at
https://account.live.com/developers/applications/index and login in with a user account.
2. Click My Apps.
Figure 68 Creating a OneDrive Application
3. Create a new application. The recommended name is CoSign - &lt;your organization
name&gt;.
4. Go to the App Settings tab.
91
7
CoSign Web App User Guide
Figure 69 OneDrive Application – App Settings
5. Record the Client ID and Client Secret values for entering in the web.config file.
6. Go to the API Settings tab
Figure 70 OneDrive Application – API Settings
92
Configuring the CoSign Web App
7
7. In the Redirect domain field, enter only the domain part of the
CloudStorageCallbackURL parameter in the web.config file (refer to
CloudStorageCallbackURL.).
For example: https://arsign.arx.com/
8. Set Mobile Client App to no.
9. Supply additional information such as Terms of Service URL and Application Logo.
10. Click Save.
11. Enter the OneDrive Client ID and Client Secret values in the SkyDriveSettings section of
the web.config file (the internal naming convention for OneDrive is SkyDrive because
SkyDrive was the former name of this Storage Cloud Service). The SkyDriveSettings
section is by default empty.
&lt; SkyDriveSettings&gt;
&lt;!-- add here SkyDrive settings--&gt;
&lt;/ SkyDriveSettings&gt;
 Enter the SkyDrive Client ID value:
&lt;add key=&quot;ClientID&quot; value=&quot;THE_VALUE&quot; /&gt;
 Enter the SkyDrive Client Secret value:
&lt;add key=&quot;ClientSecret&quot; value=&quot;THE_VALUE&quot; /&gt;
Creating a CoSign Application in Google Drive
For information on how to integrate with Google Drive, refer to the following Google
documentation:
 https://developers.google.com/drive/quickstart-cs \
 https://developers.google.com/drive/enable-sdk.
For assistance, contact ARX support.
Enabling Users to Sign from Within Google Drive
You can configure Google Drive to enable users to access CoSign Web App from the Google
Drive menu of a document that is stored inside the Google Drive web application. To do so:
1. Make sure the parameter EnableGoogleDriveIntegration in the API Settings
section of web.config is set to true.
2. Configure the Google Drive CoSign application to enable users to invoke CoSign from
within Google Drive. For assistance, contact ARX support.
93
7
CoSign Web App User Guide
Creating a CoSign Application in Box
1. Connect to the Box development portal at http://developers.box.com/ and login in with a
user account.
2. Go to the My Apps section and click Create a Box Application.
Figure 71 Managing a Box Application
3. Provide the application name. The recommended name is &lt;your organization name&gt; CoSign.
4. Click Create Application.
The following acknowledgment appears.
94
7
Configuring the CoSign Web App
Figure 72 Acknowledgment of Box Application Creation
5. Continue to configure your Box application:
Figure 73 Setting Box OAuth2 Parameters
6. Configure the OAuth2 parameters as follows:
a. Record the Client ID and Client Secret values for entering in the web.config file.
b. Select both Scopes items: Read and Write all files and folders and Manage an
Enterprise.
c. Enter a redirect_uri that points to the CoSign Web App URL, such as
https://sign.arx.com/.
7. Click Save Application.
95
7
CoSign Web App User Guide
8. Enter the Client Id and Client Secret value in the BoxSettings section of the web.config
file. The BoxSettings section is by default empty:
&lt; BoxSettings&gt;
&lt;!-- add here Box settings--&gt;
&lt;/ BoxSettings&gt;
 Enter the ClientID value:
&lt;add key=&quot;ClientID&quot; value=&quot;THE_VALUE&quot; /&gt;
 Enter the ClientSecret value:
&lt;add key=&quot;ClientSecret&quot; value=&quot;THE_VALUE&quot; /&gt;
Enabling Users to Sign from Within Box
You can configure Box to enable users to access CoSign Web App from the Box menu of a
document that is stored inside the Box web application. To do so:
1. Make sure the parameter EnableBoxIntegration in the API Settings section of
web.config is set to true.
2. Configure the Box CoSign application to enable users to invoke CoSign from within Box,
as follows:
a. In the Edit a Box Application form (Figure 72), click Create a New Web App
Integration.
Figure 74 Creating a New Web App Integration
The following General Information form appears.
96
7
Configuring the CoSign Web App
Figure 75 Creating a Box File Action
b. Edit the following parameters as follows. You may want to change other information
as well (refer to the Box developer guides).
 Supported Extensions – doc, docx, pdf, xls, xlsx
 Scoped To: select The parent folder of the file/folder from which this
integration is invoked.
 Category – Web (recommended)
 Filetype Category – Documents (recommended)
 Integration Status – Online
 New window settings – Check the Popup window will open in a tab checkbox
(recommended)
 Client Callback URL – A mandatory field. Enter the following:
https://sign.arx.com/CloudStorage/BoxFileAction/Box, where sign.arx.com is
the organizational CoSign Web App deployment location.
97
7
CoSign Web App User Guide
c. Supply the following Callback parameters:
Method
Parameter Name
Parameter value
Get
RedirectUrl
#redirect_to_box_url#
Get
FileID
#file_id#
Get
AuthCode
#auth_code#
d. Specify the following Prompt Message text: The Secure Way to Sign on the Go –
easily add digital signatures to PDF, Word and Excel documents
e. Click Save Web App Integration.
f.
When you finish configuring the application, publish your application to Box by
selecting Submit for approval (Figure 74).
Figure 76 Submitting a Box App for Approval
98
Index
—A—
Active Directory settings
enable working with AD, 72
set domain name, 72
ADFS mode
configuring for SAML2 protocol, 80
configuring for WS Federation, 74
introduction, 73
running the WS Federation utility, 75
Advantages of CoSign Web App, 7
API Integration settings, 71
Applications that work with CoSign, 3
Authenticating, data requirements, 1
Authentication, extended authentication, 68
—B—
Box
creating a CoSign app in Box, 94
enabling invoking CoSign from Box, 71, 96
invoking CoSign from Box, 65
signing documents retrieved from Box, 64
—C—
Configuring CoSign Web App, 67
CoSign
applications that work with CoSign, 3
components, 3
documentation, 4
environments supported by CoSign, 2
CoSign client
installing, 9
optimizing for CoSign Web App, 10
CoSign Web Agent, 8
Customizing CoSign Web App, 67
API Integration Settings, 71
cloud storage settings, 87
Extended Authentication Settings, 68
General Settings, 71
Image Settings, 67
SMTP Settings, 68
web.config file, 67
—D—
Data authentication systems, 1
Date and Time display in of signature, 57
Date format of signature, 57
Document appearance, 37
Document types supported, 7
Dropbox
creating a CoSign app in Dropbox, 88
signing documents retrieved from Dropbox, 59
—E—
Environments supported by CoSign, 2
Extended Authentication settings, 68
External Identity Provider (IDP)
configuration at the IDP end, 83
integrating with, 8
—F—
Forgot My Password settings, 71
—G—
General settings, 71
Google Drive
creating a CoSign app in Google Drive, 93
enabling invoking CoSign from Google Drive, 71,
93
invoking CoSign from Google Drive, 62
signing documents retrieved from Google Drive,
61
Graphical signatures
adding, 54
sketching, 55
typing in, 55
uploading a file, 55
—H—
HTTPS
redirecting HTTP to HTTPS, 18
specifying HTTPS settings, 15
—I—
Image reduction settings, 67
Installing CoSign Web App
configuring a mail server, 18
configuring if PDF forms use, 19
configuring IIS for Kerberos Ticketing, 19
installation overview, 9
installing the CoSign Client, 9
installing the Web App component, 13
using HTTPS, 15
Integrating with Cloud-based file storage services, 87
Intended audience, 5
Introduction
99
CoSign Web App User Guide
to CoSign, 2
to CoSign Web App, 7
to digital signatures, 1
—K—
Kerberos Authentication, enabling
end-user PC configuration, 85
end-user registry configuration, 86
introduction, 84
running the setspn utility, 84
web.config file modifications, 84
—L—
Logging in to CoSign Web App, 33
Logging off
redirection to a specific URL, 73
results, 58
—O—
OneDrive
creating a CoSign app in OneDrive, 91
signing documents retrieved from OneDrive, 60
Operation mode
Point of Sale, 57
standard, 57
Operational mode
setting, 57
Overview of CoSign, 1
Overview of CoSign Web App, 7
—P—
Password, changing, 56
PDF forms
filling-in, 40
prerequisite configuration, 19
prerequisite SQL server configuration, 22
prerequisite SQL server installation, 20
RAD PDF configuration, 19
required web.config file changes, 86
signing, 40
viewing, 40
POS mode
enabling for a specific user, 57
enabling globally, 72
Post-signing actions, 48
Prior knowledge, 5
—R—
RAD PDF
creating maintenance string for RadPdf database,
30
creating RadPdf database instance, 22
creating tables in RadPdf database, 27
100
enabling IIS service account to access RadPdf
database, 24
installing, 28
required for PDF forms processing, 19
Reasons for signing, 57
—S—
SAML2 protocol
configuring for ADFS, 80
running the Saml2ConfigUtility, 80
saml2configutility
executing, 80
Selecting a document, 35
from a cloud-based file management service, 36
from a local device, 35
Signature
adding graphical signatures, 54
defining date and time display, 57
defining date format, 57
defining reasons for signing, 57
defining signature appearance, 57
defining signature type, 57
defining time format, 57
Signature appearance, defining, 57
Signature Locators
disabling, 73
enabling, 73
Signature type, setting, 57
Signing a PDF document
creating a new signature, 41
post-signing actions, 48
signing a pre-existing signature field, 41
Signing an MS Office document
post-signing actions, 48
signing a pre-existing signature field, 43
Signing work flow, 33
SMTP settings, 68
—T—
Time format of signature, 57
—U—
Uninstalling CoSign Web App, 32
User settings, modifying, 56
—V—
Validating document signatures, 47
Viewing a document, 39
Viewing signature details, 46
—W—
web.config file
backing up, 67
location, 67
Index
modifying, 67
WS Federation
configuring for ADFS, 74
introduction, 73
running the Fedutil utility, 75
101
">

Halo! Saya adalah chatbot AI yang secara khusus dilatih untuk membantu Anda dengan ARX CoSign Web App Version 7.5 Digital Signature Software User Guide. Saya telah meninjau dokumen secara menyeluruh dan dapat membantu Anda menemukan informasi yang tepat yang Anda butuhkan atau menjelaskan konten dengan istilah yang jelas dan sederhana. Apakah Anda mencari panduan tentang fitur tertentu, langkah-langkah pemecahan masalah, atau penggunaan umum, jangan ragu untuk mengajukan pertanyaan Anda. Semakin banyak detail yang Anda berikan tentang kekhawatiran atau kebutuhan Anda, semakin akurat dan efektif saya dapat membantu Anda!

Asisten sedang mengetik

Asisten sedang tidak ada di depan keyboard. Silakan coba lagi nanti.

Sepertinya Anda telah mencapai dokumen yang ditulis dalam beberapa bahasa, termasuk salah satu yang bukan bahasa asli Anda. Anda dapat menggunakan tautan berikut untuk sementara menyembunyikan halaman tanpa bahasa yang Anda sukai.