[
https://issues.apache.org/jira/browse/KNOX-3101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17930706#comment-17930706
]
ASF subversion and git services commented on KNOX-3101:
-------------------------------------------------------
Commit 956abf9ccd7ba34ba3b1c0ecd0625717b5be0a2b in knox's branch
refs/heads/master from Larry McCay
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=956abf9cc ]
KNOX-3101 - hash key for RemoteAuthProvider cache (#996)
> Change RemoteAuthProvider to use a hash of the Key used for Caching
> -------------------------------------------------------------------
>
> Key: KNOX-3101
> URL: https://issues.apache.org/jira/browse/KNOX-3101
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Reporter: Larry McCay
> Assignee: Larry McCay
> Priority: Major
> Fix For: 2.2.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The initial implementation of RemoteAuthProvider caches authenticated
> Subjects locally based on the header that contained the credentials. While
> the cache is designed to provide only a few mins of caching, it is less than
> ideal to use the credentials as keys. This needs to be strengthened to use a
> hash as to not inadvertently risk leaking the credentials.
> This will require some overhead involved in the hashing so we may need to
> find something else but we shouldn't use the credentials themselves. We would
> normally have to do a hash for implementing authentication for things like
> RDMS or LDAP based passwords, etc.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
