Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ for PostgreSQL Administrator's Guide
  3. Managing PostgreSQL environment credentials
  4. Edit or delete a named credential
NetBackup™ for PostgreSQL Administrator's Guide

Edit or delete a named credential

You can edit the properties for a named credential or delete a named credential from the Credential management.

Edit a named credential

You can edit a named credential when you want to change the credential Tag, Description, Category, authentication details, or permissions. You cannot change the credential name.

To edit a named credential

  1. On the left, click Credential management.
  2. Click Edit and update the credential as needed.

    Note:

    When you update PostgreSQL instances, this action automatically starts the discovery of the PostgreSQL instance.

  3. Review the changes and click Finish.
Delete a named credential

You can delete a named credential that you no longer need to use.

Warning:

Apply another credential to any asset that uses the credential you want to delete or else backup and restore may fail for those assets.

To delete a named credential

  1. On the left, click Credential management.
  2. On the Named credentials tab, locate and click on the credential that you want to delete.
  3. Click Delete.
  4. If you are sure that you want to delete, click Delete.

Feedback

Was this page helpful?
Previous

View the credential name that is applied to an asset

Next

Protecting PostgreSQL instances and databases

Feedback

Was this page helpful?