You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Jiabao Sun (Jira)" <ji...@apache.org> on 2022/12/22 05:09:00 UTC
[jira] [Commented] (FLINK-30443) Expand list of sensitive keys
[ https://issues.apache.org/jira/browse/FLINK-30443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17651078#comment-17651078 ]
Jiabao Sun commented on FLINK-30443:
------------------------------------
I think it makes sense to expend sensitive config keys.
And make it configurable to allow users to expend them in flink-conf.yml.
> Expand list of sensitive keys
> -----------------------------
>
> Key: FLINK-30443
> URL: https://issues.apache.org/jira/browse/FLINK-30443
> Project: Flink
> Issue Type: Improvement
> Components: API / Core
> Reporter: Gunnar Morling
> Priority: Major
>
> In {{{}GlobalConfiguration{}}}, there is [a list of known configuration keys|https://github.com/apache/flink/blob/master/flink-core/src/main/java/org/apache/flink/configuration/GlobalConfiguration.java#L47-L48] whose values will be masked in log output. In our Flink deployment there's a few more keys which we would like to mask, specifically, the following ones:
> * "auth-params"
> * "service-key"
> * "token"
> * "basic-auth"
> * "jaas.config"
> While those are somewhat use-case specific, I feel they are generic enough for being added to that list, and there already is precedence in form of "fs.azure.account.key". In that light, I don't think it's worth making this somehow pluggable, but I'm curious what other folks here think. Thanks!
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)