Overview

Support for on-premises deployments, including those using Containers, ended on December 31, 2023.

For more information, please see our OneSpan Product Life Cycle page, and consult the OneSpan End of Life policy.

For any additional questions contact your Customer Service Representative.

This guide describes how to deploy OneSpan Sign in an on-premises environment using Docker containers.

This guide provides the instructions required for a basic setup. To complete the setup in your environment, you may need procedures beyond those provided in this guide. Some additional instructions are in the Application Administrator's Guide and the Platform Administrator's Guide. To obtain copies of these guides, please contact our Support Team.

The rest of this page discusses:

• Benefits of Containerization

• Coming Soon

• SaaS Only

• Deprecated Features

Benefits of Containerization

Containerization embodies an application as a single executable package that contains not only the application code, but also all the configuration files, libraries, and dependencies that the application needs to run.

Containerization provides our on-premises customers with the following benefits:

• Portability: A container creates an executable package of software that is abstracted away from (not tied to or dependent on) the host Operating System. It’s therefore portable, and can run uniformly and consistently across any platform or cloud. For example, sensitive data can stay on-premises, while less sensitive data can be stored on the public cloud.

• Speed and efficiency: Containers are often described as “lightweight”. This reflects the fact that they share the kernel of the machine’s Operating System, and so are not bogged down with its overhead. Containers don’t need to boot an Operating System, so they have shorter start times. They also increase server efficiency, decrease server costs, and reduce licensing fees.

• Ease of management: A Container Orchestration Platform automates the installation, scaling and management of containerized workloads and services. It thus eases management tasks like: (1) rolling out new versions of apps; (2) scaling containerized apps; (3) monitoring, logging and debugging.

• Security: The isolation of applications in containers prevents the invasion of malicious code from infecting other containers or the host system. In addition, security permissions can be enfored to: (1) automatically block unwanted components from entering containers; (2) limit communications with unnecessary resources.

• Wide applicability: Our containerization deploys OneSpan Sign as a Helm chart that is rendered into Kubernetes resources. To achieve maximum compatibility with real-world Kubernetes installations, our containerization does not target any specific Kubernetes system (e.g., EKS, GKE). Our solution will work with any Kubernetes-like system.

Coming Soon

The following features will be available in an upcoming OneSpan Sign Container release:

• Bulk Sending

• Transaction expiry email notification

• On-Premises HSM

SaaS Only

The following features are available only in the SaaS version of OneSpan Sign, and will not be added to the On-Premises Containerized version.

This list provides a summary of some of the features that are not currently supported in this Containerization release. It may not include all non-supported features. For more information on a specific feature, please contact our Support Team.

• Anti-virus protection

• Client APIs

• CloudHSM

• Connectors

• Data Retention

• eOriginal Vaults

• ID Verification

• Key Management System

• Remote Online Notarization

• Reporting

• Virtual Room

Deprecated Features

The following features are not supported in a container environment:

• Classic User Experience

• IBM Db2

• OneSpan Vaults

• SOAP interfaces

• e-Witness

Supported Container features can be accessed via OneSpan Sign’s REST API.