Automation V3: Using Encrypted Password Variables in Expression Editors

Overview

Previously, password variables could not be resolved in certain expression fields such as JSON bodies in Web Request steps, limiting their use in REST and SOAP API calls. Password variables are now fully supported and resolved across all applicable expression editors.

With this 3.0.5 release Provar allows you to store sensitive information, such as Client IDs and Client Secrets, as Password Variables to ensure they remain encrypted. With this enhancement, password variables can now be safely used across all supported Expression Editors without exposing sensitive values.

This enables secure injection of credentials into API requests while maintaining encryption and compliance with project security settings.

Key Benefits

• Secure reuse of encrypted credentials across all expression editors
• Consistent behavior for REST and SOAP API requests
• Improved security without limiting functionality

Supported Expression Editors

Password variables can be used in the following areas:

• Web Services (REST and SOAP)
• Custom APIs
• Page Operations
• Custom Test Steps

This applies to all fields that support expression editors, including request headers and request bodies (for example, JSON payloads).

Security and Data Protection

To ensure sensitive data remains protected:

• Password variable values are always stored and resolved in encrypted form.
• Values are never exposed in logs, test runners, or network requests.
• Sensitive data remains hidden during execution and debugging.

Encrypted Projects and Environments

Password variables continue to work seamlessly when:

1. The project is encrypted
2. The environment is encrypted

No additional configuration is required to use password variables in encrypted projects or environments.

How It Works

When a password variable is referenced in an expression editor:

• The value is securely resolved at runtime.
• The resolved value is injected into the request or operation without being logged or displayed.
• Execution proceeds normally for both REST and SOAP API calls.

Conclusion

This enhancement ensures that password variables can be used wherever expression editors are supported, allowing you to securely manage and reuse sensitive credentials without compromising visibility, execution, or encryption standards.

---

Feedback

Was this article helpful for you?

We really appreciate it!

Thank you for your feedback.

Tell us how we can improve this article.

No Yes