You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Chesnay Schepler (Jira)" <ji...@apache.org> on 2020/10/14 06:40:00 UTC

[jira] [Closed] (FLINK-19523) Secrets should be filtered out from logs

     [ https://issues.apache.org/jira/browse/FLINK-19523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chesnay Schepler closed FLINK-19523.
------------------------------------
    Fix Version/s: 1.11.3
                   1.10.3
                   1.12.0
       Resolution: Fixed

master: 43aa3fdedc0409006887c36971eccb351e2a438a
1.11: bcee07cee33c47627a3e9041af5adfd4de58d47a
1.10: ffd352e9d0f71a5e43fcc8b36f3b006fa8fb6080 

> Secrets should be filtered out from logs
> ----------------------------------------
>
>                 Key: FLINK-19523
>                 URL: https://issues.apache.org/jira/browse/FLINK-19523
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Configuration
>            Reporter: Qinghui Xu
>            Assignee: Qinghui Xu
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.12.0, 1.10.3, 1.11.3
>
>
> When jobmanager starts up, it logs configurations from jvm options and application arguments. This includes secrets (eg. "s3.secret-key").
> Ideally, secrets should be masked as it is when loading from configuration file.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)