Interface StandaloneSigningServiceData
InterfaceStandaloneSince Document Engine 1.6.0
Example
Signing document in Web standalone via NutrientViewer backend
instance.signDocument(null, {
jwt: "<auth_token>"
})
.then(function () {
console.log("The document has been signed!");
});
Properties
serverUrl
Optional
string
Base server URL to use as the signing backend.
The <server_url>/api/sign_hash is used as the signing endpoint
and <server_url>/api/get_certificates is used to retrieve the certificates.
signingToken
Optional
string
Optional signing token to be passed by the backend to the signing service. Valid only when signing via Document Engine.
Standalone only
Contains information needed for signing with Nutrient backend in standalone mode. Supports the following backends:
The document loaded in your instance will not be transferred over the network. Instead, Web SDK prepares the document locally, applies preparation options such as
flatten,position,formFieldName,appearance, andplaceholderSize, and sends only the prepared hash/bytes plus signing parameters to the backend. The backend performs the cryptographic signing, and Web SDK embeds the digital signature into the document locally.Uses JSON Web Token (JWT) to authorize with the NutrientViewer backend. See Document Engine's API Reference for more details about the JWT authorization.