Cross-Credentials Management

Feature Requests (Old)
1

Cross-Credentials Management

Actions:

  • Store API keys, tokens, and credentials securely in a vault.
  • Reuse credentials across multiple workflows without re-entering them.
  • Manage OAuth, API, and other sensitive data safely.

Use Case:
A cross-credentials management system would streamline automation by securely storing and managing authentication details. This is essential for businesses working with multiple APIs or services, ensuring security and efficiency without the need to manually re-enter credentials for each workflow, reducing risks associated with hardcoding sensitive information.

2

Hi

I am curious which vault do you use?

3

I currently don’t use a specific vault but am considering options like AWS Secrets Manager, HashiCorp Vault, or others. Do you have any recommendations or preferences for credential storage that work well in similar contexts?

4

@abuaboud - is there a suggested way for storing sensitive keys/secrets in ActivePieces currently?

Example: We need to use AWS credentials inside a Code pieces for some of our flows. I can’t see a way currently where we can store and retrieve these credentials without the values being easily viewable.

There should be a place where you can add sensitive info and be sure that once added, the value will not be viewable anywhere in the app e.g. if you returned it from a piece or console logged it.