[
https://issues.apache.org/jira/browse/FLINK-5350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15757573#comment-15757573
]
Eron Wright edited comment on FLINK-5350 at 12/17/16 9:49 PM:
---------------------------------------------------------------
I think we need to revisit how to accomplish this.
Flink installs a JAAS configuration in oder to provide a default JAAS
AppConfigurationEntry based on the configured keytab (and ticket cache too).
The ideal design would allow the user to provide a JAAS config without losing
the defaults. One approach may be to obtain the default configuration
instance (which reads from the JAAS config file) then wrap the instance in a
Flink configuration instance that provides default entries.
was (Author: eronwright):
I think we need to revisit how to accomplish this.
> Don't overwrite existing Jaas config property
> ---------------------------------------------
>
> Key: FLINK-5350
> URL: https://issues.apache.org/jira/browse/FLINK-5350
> Project: Flink
> Issue Type: Bug
> Components: Security
> Affects Versions: 1.2.0
> Reporter: Maximilian Michels
> Assignee: Maximilian Michels
> Fix For: 1.2.0
>
>
> If an existing Jaas configuration has been specified via the property
> {{java.security.auth.login.config}}, it should be used instead of overwriting
> the property.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
