[jira] [Commented] (OOZIE-1651) Oozie should mask the signature secret in the configuration output

["Alejandro Abdelnur (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OOZIE-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13860402#comment-13860402 ] 

Alejandro Abdelnur commented on OOZIE-1651:
-------------------------------------------

making the masking postfix configurable seems overkill, I would have them hardcoded.

> 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
>
>
> 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)