If you are using indirect binding, you need to provide an external LDAP username and password
in `management-server.properties` that Apigee uses to log into the external LDAP and
perform the indirect credential search.

> [!NOTE]
> **Note:** Using plain text passwords in config files may be adequate for testing purposes; however, for production environments, encryption is highly recommended.

The following steps explain how to encrypt your password:

1. Execute the following Java utility, replacing <var translate="no">YOUR_EXTERNAL_LDAP_PASSWORD</var> with your actual external LDAP password:

   ```
   java -Djava.security.properties=/opt/apigee/edge-management-server/conf/jvmsecurity.properties \
   -cp /opt/apigee/edge-gateway/lib/kernel/*:/opt/apigee/edge-gateway/lib/infra/services/*:/opt/apigee/edge-gateway/lib/thirdparty/*:/opt/apigee/edge-gateway/lib/infra/libraries/*:/opt/apigee/edge-management-server/conf/ \
   com.apigee.util.CredentialUtil \
   --password="YOUR_EXTERNAL_LDAP_PASSWORD"
   ```

   where `/opt/apigee/edge-management-server/conf/` is the path to the `credential.properties` file of the edge-management server.

   > [!NOTE]
   > **Note:** You must use Apigee's Java security file when you invoke the command to encrypt the password. This is required for both FIPS and non-FIPS enabled operating systems.

2. In the output of the command, you will see a newline followed by what looks like a random character string. Copy that string.
3. Edit `/opt/apigee/customer/application/management-server.properties`.
4. Update the following property, replacing <var translate="no">myAdPassword</var> with the string you copied from step 2, above.

   ```
   conf_security_externalized.authentication.indirect.bind.server.admin.password=myAdPassword
   ```
5. Be sure the following property is set to true:

   ```
   conf_security_externalized.authentication.indirect.bind.server.admin.password.encrypted=true
   ```
6. Save the file.
7. Restart the Management Server:

   ```
   /opt/apigee/apigee-service/bin/apigee-service edge-management-server restart
   ```
8. Verify that the server is running:

   ```
   /opt/apigee/apigee-service/bin/apigee-all status
   ```

## Testing the installation

See the testing section at the end of [Enabling
external authentication](https://docs.apigee.com/private-cloud/v4.53.00/enabling-external-authentication), and perform the same test described there.

## Testing the FIPS status

To check if your operating system is FIPS-enabled, run the following command:

```
fips-mode-setup --check
```

If the output is "`Installation of FIPS modules is not completed. FIPS mode is disabled.`", then your operating system is not FIPS-enabled.

See [Edge for Private Cloud on FIPS-enabled RHEL 8.X](https://docs.apigee.com/private-cloud/v4.53.00/fips-enabled-rhel-8x) to know how to enable FIPS mode on RHEL 8.X.