Component Server Vault Proxy

Browse the API description using OpenAPI.

A Vault proxy dedicated to the component server allows to safely manage credential encryption when operating in a Cloud environment.

Vault proxy

The Vault Proxy only concerns data marked as @Credential in the component configuration.

This Vault proxy:

  • receives an encrypted payload containing sensitive data from the remote engine, via HTTP.

  • decrypts the data

  • caches in memory the decrypted value of the data for performance reasons.

  • sends unencrypted data to the component server using HTTPS. An SSL certificate can be automatically generated and secures the data.

Vault proxy configuration

the configuration is read from system properties, environment variables, …​.

Default value: false. Should any certificate be accepted - only for dev purposes.


Default value: 64. Thread pool core size for Component Server client.


Default value: 60000. Thread keep alive (in ms) for Component Server client thread pool.


Default value: 256. Thread pool max size for Component Server client.


Default value: 64. Thread pool core size for Vault client.


Default value: 60000. Thread keep alive (in ms) for Vault client thread pool.


Default value: 256. Thread pool max size for Vault client.


JAX-RS fully qualified name of the provides (message body readers/writers) for vault and component-server clients.


The token to use to call component-server if any.


Where the keystore to use to connect to Component Server is located.


Default value: changeit. The keystore password for talend.vault.cache.client.server.certificate.keystore.location.


The keystore type for talend.vault.cache.client.server.certificate.keystore.location.


The truststore type for talend.vault.cache.client.server.certificate.keystore.location.


Default value: localhost,,0:0:0:0:0:0:0:1. Valid hostnames for the Component Server certificates (see


Default value: 30000. HTTP connection timeout to vault server.

Default value: 30000. HTTP read timeout to vault server.


Where the keystore to use to connect to vault is located.


Default value: changeit. The keystore password for talend.vault.cache.client.vault.certificate.keystore.location.


The keystore type for talend.vault.cache.client.vault.certificate.keystore.location.


The truststore type for talend.vault.cache.client.vault.certificate.keystore.location.


Default value: localhost,,0:0:0:0:0:0:0:1. Valid hostnames for the Vault certificates (see


Default value: 3600. JCache expiry for decrypted values (ms).

Default value: false. Should JCache MBeans be registered.


Default value: false. Should JCache statistics be enabled.

Default value: `. JCache `CacheManager properties used to initialized the instance.


Default value: geronimo:// Configuration for JCache setup, default implementation is Geronimo Simple Cache.


Default value: 100000. JCache max size per cache.


Default value: 30000. How often (in ms) the Component Server should be checked to invalidate the caches on the component parameters (to identify credentials).

Default value: localhost,,0:0:0:0:0:0:0:1. The IP or hosts allowed to call that server on /api/* if no token is passed.

Default value: none. Enable to sanitize the hostname before testing them. Default to none which is a noop. Supported values are docker (for <folder>_<service>_<number>.<folder>_<network> pattern) and weave (for <prefix>_dataset_<number>.<suffix> pattern).

Default value: -. The tokens enabling a client to call this server without being in allowedIp whitelist.


Default value: 422. Status code sent when vault can’t decipher some values.


Default value: 600000. How often (in ms) to refresh the vault token.


Default value: 10000. How often (in ms) to refresh the vault token in case of an authentication failure.


Default value: vault\:v[0-9]+\:.*. The regex to whitelist ciphered keys, others will be passthrough in the output without going to vault.


Base URL to connect to Component Server


Default value: v1/auth/engines/login. The vault path to retrieve a token.


Default value: -. The vault role identifier to use to log in (if token is not set). - means it is ignored.


Default value: -. The vault secret identifier to use to log in (if token is not set). - means it is ignored.


Default value: -. The vault token to use to log in (will make roleId and secretId ignored). - means it is ignored.


Default value: v1/tenants-keyrings/decrypt/{x-talend-tenant-id}. The vault path to decrypt values. You can use the variable {x-talend-tenant-id} to replace by x-talend-tenant-id header value.


Base URL to connect to Vault.

Configuration mechanism

The configuration uses Microprofile Config for most entries. It means it can be passed through system properties and environment variables (by replacing dots with underscores and making the keys uppercase).

To configure a Docker image rather than a standalone instance, Docker Config and secrets integration allows you to read the configuration from files. You can customize the configuration of these integrations through system properties.

Docker integration provides a secure: support to encrypt values and system properties, when required.

It is fully implemented using the Apache Geronimo Microprofile Config extensions.

Adding the Vault Proxy to your Docker Compose

The YAML below is the recommended configuration to enable the Vault Proxy and Component Server to communicate over HTTPS.

Docker Compose

version: '3.2'

  component-server: (1)
      timeout: 3s
      interval: 3s
      retries: 3
      test: curl --fail http://localhost:8080/api/v1/environment
    image: tacokit/component-server:${COMPONENT_SERVER_IMAGE_VERSION:-1.1.6_20190208104207}
        -Dtalend.component.server.filter.secured.tokens=vault-proxy (2) (3)
        -Dtalend.component.server.ssl.keystore.location=/opt/talend/configuration/https.p12 (3)
        -Dtalend.component.server.ssl.keystore.type=PKCS12 (3)
        -Dtalend.component.server.component.registry=/opt/talend/connectors/ (4)
        -Dtalend.component.server.maven.repository=/opt/talend/connectors (4)
    - connectors:/opt/talend/connectors:ro  (4)
    - vault-proxy-configuration:/opt/talend/configuration (3)

  component-server-vault-proxy: (5)
      timeout: 3s
      interval: 3s
      retries: 3
      test: curl --fail http://localhost:8080/api/v1/proxy/environment
    image: tacokit/component-server-vault-proxy:${COMPONENT_SERVER_VAULT_PROXY_IMAGE_VERSION:-1.1.6_20190208104221}
        -Dtalend.vault.cache.client.server.certificate.keystore.location=/opt/talend/configuration/https.p12 (6)
        -Dtalend.vault.cache.client.server.certificate.keystore.type=PKCS12 (6)
        -Dtalend.vault.cache.client.server.hostname.accepted=component-server (6)
        -Dtalend.vault.cache.client.server.authorization=vault-proxy (7)
        -Dtalend.vault.cache.talendComponentKit.url=https://component-server:8080/api/v1 (7)
        -Dtalend.vault.cache.vault.url=http://vault:8200 (8)
        -Dtalend.vault.cache.vault.auth.roleId=myrole (8)
        -Dtalend.vault.cache.vault.decrypt.endpoint=v1/something/decrypt/00000001 (8)${COMPONENT_SERVER_VAULT_PROXY_CLIENT_IP:-} (9)
    - 9090:8080/tcp
    links: (10)
    - "component-server:component-server"
    # - "vault:vault"
    - vault-proxy-configuration:/opt/talend/configuration:ro

  connectors: (11)
    - CONNECTORS_SETUP_OPTS=setup --wait-for-end
    - connectors:/opt/talend/connectors:ro

volumes: (12)
1 The standard Component Server entry.
2 Ensures only a client with a particular token can call the server. It is similar to a shared secret and only allows to call the server in "remote" mode, since only the local mode is enabled by default.
3 Activates and configures the auto generation of a X.509 certificate which is used for the HTTPS connector on the server.
4 Binds the components to deploy into the server.
5 Definition of the Vault proxy service which handles the mediation between Vault and the Component Server.
6 Since both servers are colocalized, the generated certificate is inherited from the Component Server, which allows to create the client that connects to it.
7 Configuration of the base URL to connect to the server - see <10>.
8 Configuration of the vault connection and security information.
9 Ensuring that connecting from $COMPONENT_SERVER_VAULT_PROXY_CLIENT_IP to vault proxy is possible. Any other IP will be rejected.
10 Linking both services so they can communicate. It allows not to expose the Component Server port outside of its own container (no ports mapping in the Component Server service definition). Note that if your vault is a service, you can link it here as well.
11 Common component image service definition.
12 Volumes used by the services. The connectors has not changed but vault-proxy-configuration was added for the automatic HTTPS configuration.

This setup enables the Vault Proxy and Component Server to communicate. You can now use the Vault Proxy as if it was the Component Server, by using localhost:9090 (or any other host matching your deployment) instead of the Component Server directly.

Linking the Vault Proxy to the Component Server through HTTPS

When the Vault Proxy is enabled, ensure you configure HTTPS on the Component Server using the following parameters:

true or false. Indicates if the SSL protocol is enabled.


Keystore password.


Path to Keystore.


Private key/certificate alias.


Keystore type.


true or false.


Specifies if a custom command is to be used to generate the certificate.


Encryption algorithm. RSA by default.


Distinguished name.


Size of the key. 2048 by default.


SSL port to use.

Adding extensions to the instance

You can mount a volume in /opt/talend/component-kit-vault-proxy/custom/ and the jars in that folder which will be deployed with the server. Since the server relies on CDI (Apache OpenWebBeans) you can use that technology to enrich it, including JAX-RS endpoints, interceptors etc…​or just libraries needing to be in the JVM.

Scroll to top