Sign documents & images in the Cloud with GroupDocs.Signature REST APIs.
376
Product Page | Docs | Demos | Swagger UI | Examples | Blog | Search | Free Support | Free Trial
GroupDocs.Signature REST API allows the developers to create, remove, verify and search signature objects (text, stamp, image, barcode & digital) in a number of document formats including Word documents, Excel spreadsheets, PowerPoint presentations, PDF, OpenDocument formats & images.
This Docker image makes it possible to use GroupDocs.Signature Cloud API on a single machine or integrate into your existing application or system solution.
GroupDocs.Signature can be started in trial or licensed modes. Optionally you can enable authentication by setting predefined credentials.
To start the container and run GroupDocs.Signature Cloud in trial mode type the following.
docker run `
-p 8080:80 `
-v "${pwd}/data:/data" `
--name signature_cloud `
groupdocs/signature-cloud
docker run \
-p 8080:80 \
-v $(pwd)/data:/data \
--name signature_cloud \
groupdocs/signature-cloud
Wait for the startup process to complete you should see the following log:
info: GroupDocs.Signature.Cloud.Web.Startup[0]
"License" parameters are omitted, the app works in trial mode.
...
As you can see from the messages above GroupDocs.Signature Cloud is working in a trial mode so the following trial limitations are applied:
Note: You can find more information about licensing and request a temporary license at https://purchase.groupdocs.cloud/trial
In case you already have the license keys, you can run GroupDocs.Signature Cloud in licensed mode. To do so, pass license private and public keys as environment variables as shown below.
docker run `
-p 8080:80 `
-v "${pwd}/data:/data" `
-e "LICENSE_PUBLIC_KEY=public_key" `
-e "LICENSE_PRIVATE_KEY=private_key" `
--name signature_cloud `
groupdocs/signature-cloud
docker run \
-p 8080:80 \
-v $(pwd)/data:/data \
-e LICENSE_PUBLIC_KEY=public_key \
-e LICENSE_PRIVATE_KEY=private_key \
--name signature_cloud \
groupdocs/signature-cloud
After the container is started you should see the message that indicates that license has been set successfully.
info: GroupDocs.Signature.Cloud.Web.Startup[0]
The license has been set.
...
To enable authentication set CLIENT_ID/CLIENT_SECRET parameters as it shown below. Please note that, authentication is required in case you're going to use SDK. The TOKEN_SECRET is used as the symmetric key for signing JWT tokens with the HMAC-SHA256 algorithm. • If the TOKEN_SECRET environment variable is set, its value will be used as the signing key. • If the TOKEN_SECRET is not set, the application will generate a random 256-bit secret at runtime. This random secret is not persisted and will change every time the application restarts.
docker run `
-p 8080:80 `
-v "${pwd}/data:/data" `
-e "CLIENT_ID=client_id" `
-e "CLIENT_SECRET=client_secret" `
-e "TOKEN_SECRET=aifvtf67769fydrdjh089y86f7cfnr6e5ev856db7ii8t787rtb6r689f07t897tk907tn8f6b68d987yh0u" `
--name signature_cloud `
groupdocs/signature-cloud
docker run \
-p 8080:80 \
-v $(pwd)/data:/data \
-e CLIENT_ID=client_id \
-e CLIENT_SECRET=client_secret \
-e TOKEN_SECRET=aifvtf67769fydrdjh089y86f7cfnr6e5ev856db7ii8t787rtb6r689f07t897tk907tn8f6b68d987yh0u \
--name signature_cloud \
groupdocs/signature-cloud
By default, a local storage used inside container for file operations. It's possible to connect a Google Cloud storage by setting GOOGLE_APPLICATION_CREDENTIALS and GOOGLE_STORAGE_BUCKET environment variables.
docker run `
-p 8080:80 `
-v "${pwd}/data:/data" `
-e "GOOGLE_APPLICATION_CREDENTIALS=/data/key.json" `
-e "GOOGLE_STORAGE_BUCKET=bucket_id" `
--name signature_cloud `
groupdocs/signature-cloud
docker run \
-p 8080:80 \
-v $(pwd)/data:/data \
-e GOOGLE_APPLICATION_CREDENTIALS=/data/key.json \
-e GOOGLE_STORAGE_BUCKET=bucket_id \
--name signature_cloud \
groupdocs/signature-cloud
You can check service status by calling GET http://localhost:8080/once the container and GroupDocs.Signature Cloud has been started. The successful response status is 200 which means that service is up and running.
Invoke-WebRequest -Uri http://localhost:8080/
curl -i http://localhost:8080/
After starting, you can use Swagger UI at http://localhost:8080/swagger/ and start exploring the API.
To stop the running Docker container, just use Ctrl+C in the same terminal where the container is running. Alternatively, you can stop the container by name as shown below.
docker stop signature_cloud
| Mount path in container | Description |
|---|---|
| /data | Folder with documents to process |
| Name | Description |
|---|---|
| LICENSE_PUBLIC_KEY | Public key of the license |
| LICENSE_PRIVATE_KEY | Private key of the license |
| CLIENT_ID | Predefined client ID (requied when using SDK) |
| CLIENT_SECRET | Predefined client secret key (requied when using SDK) |
| TOKEN_SECRET | The symmetric key for signing JWT tokens |
| GOOGLE_APPLICATION_CREDENTIALS | Path to json file containing Google Cloud Storage Credentials (can be obtained in Google Cloud Console) |
| GOOGLE_STORAGE_BUCKET | Name of Google Cloud Storage bucket, where files should be stored |
We generate our SDKs in different languages so you may check if yours is available in the following list. If you don't find your language, feel free to request for it on our Support Forums, or use raw REST API requests as detailed on GroupDocs.Signature Cloud for cURL.
| .NET | Java | PHP | Python | Ruby | Node.js |
|---|---|---|---|---|---|
| GitHub | GitHub | GitHub | GitHub | GitHub | GitHub |
| NuGet | Maven | Composer | PIP | GEM | NPM |
Product Page | Docs | Demos | Swagger UI | Examples | Blog | Search | Free Support | Free Trial
Content type
Image
Digest
sha256:7543d1e91…
Size
308.8 MB
Last updated
10 months ago
Requires Docker Desktop 4.37.1 or later.