[
https://issues.apache.org/jira/browse/OOZIE-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13860619#comment-13860619
]
Robert Kanter commented on OOZIE-1651:
--------------------------------------
I think it makes sense to hardcode the full property names because what we're
really trying to do is mask those two properties. We can also make the code a
little more efficient because we're not doing partial matches. If we later add
a new property that is sensitive, it can simply be added to the list.
> Oozie should mask the signature secret in the configuration output
> ------------------------------------------------------------------
>
> Key: OOZIE-1651
> URL: https://issues.apache.org/jira/browse/OOZIE-1651
> Project: Oozie
> Issue Type: Bug
> Components: security
> Affects Versions: 3.3.2, 4.0.0
> Reporter: Robert Kanter
> Assignee: Robert Kanter
> Priority: Critical
> Attachments: OOZIE-1651.patch, OOZIE-1651.patch, OOZIE-1651.patch,
> OOZIE-1651.patch
>
>
> The value of {{oozie.authentication.signature.secret}} is the secret that's
> used to sign the cookies/tokens crated by Oozie for authentication after
> Kerberos. If a malicious user were to find out this secret, they could forge
> counterfeit cookies/tokens as any user with any expiration date.
> Oozie exposed the configuration properties via its REST API. It currently
> only masks any properties that end with ".password" (i.e.
> {{oozie.service.JPAService.jdbc.password}}). We should expand this to also
> mask the signature secret.
> In fact, it would be useful to generalize this ability to add a property that
> masks something the user can configure.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
