Skip to Content

Manage endpoint credentials in Jitterbit Studio

Introduction

Storing credentials directly in a connection configuration creates two risks: credentials are visible to anyone with project access, and they must be manually updated whenever a password changes or a user account is deprovisioned. This page covers how to manage credentials securely using project variables and system accounts.

Endpoint credentials

We recommend using a system ID with administration permissions for endpoint credentials, rather than a user-level ID. User IDs typically expire or have to be disabled when a user leaves a company.

By using project variables (whose values can be hidden) for credentials management, a Harmony organization administrator does not have to enter production credentials. By setting up the appropriate user permissions, a user can apply the production credentials through the Management Console Projects page.

If using private agents, as an alternative to using the Management Console, global variables can be managed using the [PredefinedGlobalVariables] section of the private agent configuration file.

Create a hidden project variable

  1. In Studio, open the project actions menu and select Project Variables.

  2. Click Add.

  3. Enter the variable Name (for example, db.password) and its Value.

  4. Enable Hide value to prevent the value from appearing in operation logs or project exports.

  5. Click Save.

To reference the variable in a connection field, use bracket syntax: [db.password]. Studio substitutes the stored value at runtime without exposing it in logs.

For guidance on naming credential variables consistently, see Use a naming convention for variables. For guidance on reusing a single endpoint across multiple operations, see Reuse endpoints and scripts.