[ https://issues.apache.org/jira/browse/HADOOP-10607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14010301#comment-14010301 ]
Owen O'Malley commented on HADOOP-10607: ---------------------------------------- Larry, here are some additional comments: * CredentialEntry.toString should assume use the characters as-is rather than printing the hex. * I'd suggest removing getCredentialEntryFromConfigValue. I think we can have a better backwards compatibility story. ** create an IdentityProvider that returns the alias as the password. ** make IdentityCredentialProvider the default Thus, hive-site.xml can use "javax.jdo.option.ConnectionPassword" as "mysecret" and the default of the IdentityCredentialProvider will return "mysecret" as the password. When the user updates their provider to a more secure alternative, they would change "mysecret" to "hive-db-password" and set the password in their provider for "hive-db-password". Does that sound reasonable? > Create an API to Separate Credentials/Password Storage from Applications > ------------------------------------------------------------------------ > > Key: HADOOP-10607 > URL: https://issues.apache.org/jira/browse/HADOOP-10607 > Project: Hadoop Common > Issue Type: New Feature > Components: security > Reporter: Larry McCay > Assignee: Larry McCay > Fix For: 3.0.0 > > Attachments: 10607-2.patch, 10607-3.patch, 10607-4.patch, > 10607-5.patch, 10607.patch > > > As with the filesystem API, we need to provide a generic mechanism to support > multiple credential storage mechanisms that are potentially from third > parties. > We need the ability to eliminate the storage of passwords and secrets in > clear text within configuration files or within code. > Toward that end, I propose an API that is configured using a list of URLs of > CredentialProviders. The implementation will look for implementations using > the ServiceLoader interface and thus support third party libraries. > Two providers will be included in this patch. One using the credentials cache > in MapReduce jobs and the other using Java KeyStores from either HDFS or > local file system. > A CredShell CLI will also be included in this patch which provides the > ability to manage the credentials within the stores. -- This message was sent by Atlassian JIRA (v6.2#6252)