Regenerate the database user’s password from the PD DigitalOcean Kafka service page when you intend to replace that credential. Applications using the old password need to be updated.

Prepare dependent applications

Identify the applications using this service and arrange how you will update their stored credential. Confirm the correct database service before making the change. Regeneration is a credential change, not a cluster rebuild or data migration.

Request the new password

1. Open the client service’s Information page.
2. Choose Regenerate password and review the confirmation. Enable Client: Connection details for the package.
3. Read the result before doing anything else. If successful, reopen View connection details to obtain the saved password.
4. Update the intended applications through their normal credential settings and check their connections with the same host, port and TLS configuration.

The provider can take time to apply the reset. Do not promise that a new password takes effect immediately, or repeatedly regenerate it while testing with an older copy.

When the new password cannot be shown

The provider may have changed the password even if it was not returned or could not be saved to the service. An error message is not proof that the old credential still works. Establish the current provider and saved service credential before reconnecting or trying another reset.

Verify the outcome

Check an actual application connection after updating its credential. A recorded Password regenerated activity entry alone does not prove every dependent application has been updated. Keep either password and any full connection string out of shared screenshots.

See the PD DigitalOcean Kafka Blesta guide for related setup, or explore PD DigitalOcean Kafka.