Client Web

The SignServer Client Web is one of the available client interfaces for SignServer. The Client Web supports signing documents, validating documents, and validating certificates using Workers configured through an administrative interface, such as the Admin Web.

Access

The SignServer Client Web interface can be accessed using a web browser on the default location: /signserver/clientweb/

HTTPS with client certificate or OpenID Connect authentication is required (read more on the Login and Logout page), using port 8443 which is then set up to require client certificate or a valid Identity Provider authentication.

For a local installation, the address would typically be: https://localhost:8443/signserver/clientweb/

Client Web Pages

The following lists the Client Web pages available for selection in the navigation bar. For more information on the Client Web "landing" page, see Main Page for the Admin Web.

File Upload

On the File Upload page, you can upload a file to be signed or validated.

Field	Description
Name	Provide the name for a Worker already configured on the server.
File	Upload the file under the Browse… button.
Process type	Choose the type of process you want to perform: Sign document, Validate document, or Validate certificate.
CMS-Specific	Choose the type of signature to request: default, detached, or include content. The default is specified in the Worker.
PDF-Specific	Provide the password for the pdf, if needed.
Generic meta data	Input data as part of the request, using the Worker properties and request parameters. You can override a feature or a property if it has been enabled in the Worker. Depending on the chosen Worker, different parameters are supported. Ensure that entered parameters are supported in property descriptions in Worker pages. Example for client-side hashing If you would like to use client-side hashing with a CMS Signer, the following properties need to be provided as request metadata: `USING_CLIENTSUPPLIED_HASH=true` (unless the signer is configured with CLIENTSIDEHASHING=true) `CLIENTSIDE_HASHDIGESTALGORITHM=SHA-256` (or with the name of the hash algorithm used to digest the data)

After filling out the fields, click Submit to create the signed file.

Direct Input

On the Direct Input page, you can input data to be signed.

Field	Description
Name	Provide the name for a Worker already configured on the server.
Data	Provide raw text data to be signed as input. If the raw text is a hash to be signed, use the Generic meta data section to specify the parameters.
Encoding	Specify the encoding of the data: None: Sent to the server to be hashed. Base64: Hash already encoded, provide in the generic meta data field.
Process type	Choose the type of process you want to perform: Sign document, Validate document, or Validate certificate.
CMS-Specific	Choose the type of signature to request: default, detached, or include content. The default is specified in the Worker.
PDF-Specific	Provide the password for the pdf, if needed.
Generic meta data	Input data as part of the request, using the Worker properties and request parameters. You can override a feature or a property if it has been enabled in the Worker. Depending on the chosen Worker, different parameters are supported. Ensure that entered parameters are supported in property descriptions in Worker pages.

After filling out the fields, click Submit to create the signed file.

More…

The More page provides a form for using MRTD SOD signing.

The MRTD SOD Signer creates the Complete Security Object (SOd) for Machine Readable Travel Documents (MRTD), such as electronic passports and residence permits, by signing the provided data groups (DGs).

This form submits data groups to be stored on a MRTD.

Field	Description
Name	Provide the name for a Worker already configured on the server.
Input	Provide the data groups (DG) for signing.
Encoding	Specify the encoding of the data: None: Sent to the server to be hashed. Base64: Hash already encoded, provide in the generic meta data field.
Request LDS version	Specifies the version of Logical Data Structure (LDS). Define the value based on the LDS version: Unspecified, v1.7, or v1.8.
Unicode Version	Specifies the version of Unicode used in the datagroups. Required if LDS 1.8 is used. Example: 040000 for Unicode version 4.0.0.
Generic meta data	Input data as part of the request, using the Worker properties and request parameters. You can override a feature or a property if it has been enabled in the Worker. Depending on the chosen Worker, different parameters are supported. Ensure that entered parameters are supported in property descriptions in Worker pages.

After filling out the fields, click Submit to create the signed file.

Using the Other Actions, you can also choose to display or download the signer certificate.