Skip to main content
Version: 4.42

Sign Service integration

Overview​

In this tutorial, you will learn how to integrate Sign Service, a server-side digital signing solution that centralizes certificate management and enforces access control using token-based authentication.

This tutorial is intended for developers and IT administrators. To follow it, a basic understanding of HTTP APIs, bearer token authentication, and digital certificates is helpful.

Background​

This integration allows your application to use the centralized digital certificates from Redtrust to securely sign documents through Sign Service.

Redtrust's Sign Service manages the entire signing workflow, including user authentication, token issuance, certificate management, and signature execution, through a centralized and secure API.

The integration flow consists of two main phases:

  1. Authentication and token retrieval: The user authenticates against Redtrust and obtains an access token that authorizes access to the signing service.
  2. Document signing using Redtrust certificates: Once authenticated, your application can perform signing operations using the digital certificates managed by Redtrust.

Before you begin​

To integrate the service, you need the following information provided by the Redtrust customer:

  • IP address or host name of the Redtrust server.
  • The port used to access Sign Service (default is 8083).
  • The client_id that Redtrust assigns to your application.
  • (Optional) Domain name.

In addition, the Redtrust administrator must register your application's redirect URI for the service in advance. See Configure the redirect URIs.

Step 1: Authenticate and get an access token​

Authenticate the user with the OAuth 2.0 authorization code flow with PKCE to obtain an access token. For the full flow, including endpoints, parameters, and token renewal, see Sign API authentication.

Include the access token in the Authorization header of all Sign API calls:

Authorization: Bearer YOUR_ACCESS_TOKEN

Step 2: Sign documents​

Signing requests are made to the following base URL:

https://YOUR_REDTRUST_IP:PORT/signapi

For example https://localhost:8083/signapi/v1/sign/document or https://localhost:8083/signapi/v1/certificate/list.

To complete the signing process, use the endpoints described in the Sign API reference.

Additional resources​

Was this page helpful?