> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuring JD Credentials

> Set JD SPB authentication for the Bank Transfer plugin in Lerian Console — Legacy Code, User Code, password, and RSA PEM private key for signing.

The **JD Credentials** section holds the details the Bank Transfer plugin uses to authenticate against the JD SPB integration. Without these values, the plugin cannot send or receive transfers.

The section header shows a **Configured** or **Not Configured** badge. It reads **Configured** when both a Legacy Code and a User Code have a value.

## Accessing the section

***

<Steps>
  <Step title="Open Settings">
    In the Bank Transfer sidebar, click **Settings**.
  </Step>

  <Step title="Expand JD Credentials">
    The section sits first on the page and opens by default.
  </Step>
</Steps>

## Fields

***

### Legacy Code

The legacy client identifier from JD. The form does not require this field. The JD integration usually needs a value here to authenticate.

### User Code

The user identifier for the credentials. The form does not require this field. The JD integration usually needs a value here to authenticate.

### Password

The password for the user. The plugin stores it as a secret and never shows it after you save. The field shows placeholder dots instead of the stored value. Leave it empty when you save to keep the current password.

### Private Key (PEM)

The PEM-encoded private key that signs requests to JD. It must be an **RSA** key in PEM format. JD SPB signatures use RSA PKCS#1 v1.5 with SHA-256. The key must have at least **3072 bits**.

The plugin also stores it as a secret and never shows it back. The field shows placeholder dots. Leave it empty to keep the current value.

### Signature Required

Controls whether the plugin signs requests to JD with the private key. Keep it on for production transfers. Outbound TED signing is mandatory, and the plugin rejects unsigned dispatch outside local test use.

<Warning>
  Treat the Legacy Code, User Code, Password, and Private Key as production secrets. Restrict edit access. Do not share screenshots that show these fields. Rotate the values through your organization's standard secret-rotation process.
</Warning>

## Saving changes

***

After you edit the fields, click **Save** in the toolbar at the top of the page. The plugin submits only the fields you changed. Secret fields left empty keep their current stored value.

The plugin records every change in the [Settings History](/en/rails/ted/console/bt-viewing-settings-history) tab. It stores secret values but shows them as masked placeholders (`••••`). You can see *when* a secret changed without exposing its content.