-
-
Notifications
You must be signed in to change notification settings - Fork 92
Description
Is your feature request related to a problem? Please describe.
Currently, sensitive data such as encrypted global variables variables.secret_data=ENC(...) is displayed in plaintext in the Allure report. Although such values are masked in logs, they remain exposed in the report, which poses a security risk.
Describe the solution you'd like
Introduce a configuration property (e.g., report.mask-secret-data, defaulting to false) that enables automatic masking of sensitive information in the Allure report. When enabled, the framework should detect and mask any value following the ENC(...) pattern
Describe alternatives you've considered
Additionally, an optional property like report.sensitive-variables could be provided to list specific variable names that should be masked.
Not sure how the masking should be implemented internally, but I’m leaning towards displaying variables in their encrypted form: exactly as they are stored in properties files (e.g., ENC(...)). This way, if needed, the data can still be decrypted using a secure key to verify the correctness of the input, without exposing sensitive data.
Additional context
Allure reports are published automatically in test pipelines. In shared environments like Kubernetes, this can broaden access to sensitive data. Masking encrypted values in reports would provide an additional layer of security, while still allowing controlled access to the decrypted values when necessary (with the right key).