Skip to main content

Sample integrations

This section provides example integrations that show how to use the CyberArk Code Sign Client with common signing tools and build systems. These examples are designed to help you get started quickly by demonstrating how to configure the client, reference Signing Keys, and perform signing operations in real-world environments.

What these examples are — and what they are not​

The examples in this section illustrate how to use the Code Sign Client with popular signing tools such as Signtool, jarsigner, apksigner, openssl, and others. They are meant to:

  • Demonstrate typical configuration patterns
  • Show how Signing Keys are accessed through the Code Sign Client
  • Help you adapt the approach to your own tools and workflows

The examples do not represent a list of officially supported signing applications. Because the Code Sign Client exposes keys through standard cryptographic interfaces (PKCS#11 or CSP/KSP), it can work with any signing tool that supports those interfaces. You can use these samples as templates and apply the same concepts to other tools in your environment.

How to use the sample integrations​

Each example includes:

  • Required client configuration steps
  • Environment variables or parameters needed by the external tool
  • A complete sample command or workflow
  • Notes about compatibility or caveats when using that tool with the Code Sign Client

These examples assume:

  • The Code Sign Client is installed
  • The client has been authenticated (either with a user API key or a service account)
  • You have access to at least one Signing Key

If you have not completed installation or authentication, start here:

Available examples​

Tool-specific integration examples (apksigner, jarsigner, Signtool, OpenSSL, pkcs11tool, PowerShell, Sigstore cosign, U-Boot mkimage, and others) are available in the Code Sign Manager documentation.

Each example shows how to connect a Signing Key obtained through the Code Sign Client to a specific signing tool or process, including:

  • Required client configuration steps
  • Environment variables or parameters needed by the tool
  • Complete sample commands or workflows
  • Compatibility notes and caveats