Description
PDFSign Builder is a tool to add digital signatures to PDF files. Its REST interface allows a three-phase signature:
- Upload the document to sign and obtain a hash to be signed. After uploading the file, a hash can be obtained which must be signed by any third process
- Generate a PKCS#7 structure using the private key corresponding to the certificate informed in phase 1.
- Compose the signed document attaching the structure informed in phase 2.
Its services can be configured to respond over an HTTP or HTTPS protocol, and it is available as Docker distribution.
Service
PDFSign builder responds to the requests in a unique URL defined in its configuration file. Different configurations can be accessed using the X-Tenant header variable.
At least a general configuration must be defined so that the service can be started.
Step 1- Download Docker image
In order to download the images, the user must be registered in the aforesaid platform. Contact CertiSur to request access, and inform the Docker Hub profile to grant access to the docker image.
Login using a Docker Hub account:
# docker login -u <docker hub account> Password: WARNING! Your password will be stored unencrypted in /root/.docker/config.json. Configure a credential helper to remove this warning. See https://docs.docker.com/engine/reference/commandline/login/#credentials-store Login Succeeded
Inform your docker hub account
You have to inform your docker hub account in order to authorize to download the package. Send an email to support@certisur.com.
Security warning
It is possible to save the user’s credentials so as to login safely following the steps on this link (https://docs.docker.com/engine/reference/commandline/login/#credentials-store).
Step 2- Pulling an image from Docker
# docker pull certisursa/pdf-signer-backend:latest latest: Pulling from certisursa/pdf-signer-backend a02a4930cb5d: Pull complete b5ffff9dbcda: Pull complete ... 7e5f58de12ac: Pull complete Digest: sha256:332ee89371399b7c6235465beb00fbd2071868fecee33fc14d04b87ba99b265d Status: Downloaded newer image for certisursa/pdf-signer-backend:latest docker.io/certisursa/pdf-signer-backend:latest
Step 3- Run pdf-signer-backend docker image
To run pdf-signer-backend container you have to execute the following command line:
# docker run -d \ -it \ -p <external_port>:8080 \ -v <pdf-signer-backend_config_folder>:/app/config/ \ -v <df-signer-backend_log_folder>:/app/log/ \ -v <df-signer-backend_repository_folder>:/app/repository/ \ pdf-signer-backend
It is necessary to overwrite the directory where the configuration of the tenants is located. The volume configuration explained below.
Volumes
The following volumes must be mounted on the Docker image to overwrite the variables of each defined tenant.
| Source (host) | Path (container) | Description |
|---|---|---|
| /home/opera/docker/pdf-signer-backend/config | /app/config | configuration files |
| /home/opera/docker/pdf-signer-backend/log | /app/log | log files |
| /home/opera/docker/pdf-signer-backend/repository | /app/repository | doc repository |
Step 4- Test pdf-signer-backend
Execute the following command to run default pdf-signer-backend docker container
# docker run -d \ -it \ --name pdf-signer-backend \ -p 8080:8080 \ certisursa/pdf-signer-backend:latest
Open your browser pointing to http://localhost:8080/signer/v1/healthcheck (or the port defined by you) to access the URL where you published your PDFSign Builder installation. You'll see the following image.
| If you can see this image means that your service is running into your docker container. |
|
Debbie default configuration
Debbie docker image includes an ACME tenant inside. You must overwrite that definition to include your own company or project tenants.