hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Larry McCay (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-12076) Incomplete Cache Mechanism in CredentialProvider API
Date Wed, 10 Jun 2015 19:42:00 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-12076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14580978#comment-14580978

Larry McCay commented on HADOOP-12076:

I just played around with more test code to check your last question.

bq. Does the loaded KeyStore recognize (non-deleted) changes to the underlying file after
it's been loaded? It's possible that while the file still exists the keystore could use filesystem
stat calls to find out if it has changed and update its cache as appropriate.

I created a new provider and added a new password and persisted the keystore then attempted
to get it from the older provider and it returns null as I expected.

The values are loaded at provider creation - any added credentials that are needed by a running
process requires a restart or a new provider instance.

> Incomplete Cache Mechanism in CredentialProvider API
> ----------------------------------------------------
>                 Key: HADOOP-12076
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12076
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>            Reporter: Larry McCay
>            Assignee: Larry McCay
>         Attachments: HADOOP-12076-001.patch
> The AbstractJavaKeyStoreProvider class in the CredentialProvider API has a cache member
variable and interrogation of it during access but does not populate it.

This message was sent by Atlassian JIRA

View raw message