[
https://issues.apache.org/jira/browse/HADOOP-15765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16618940#comment-16618940
]
Steve Loughran commented on HADOOP-15765:
-----------------------------------------
+[~lmccay] [~daryn]
that case statement does seem to have grown over time, so configurability is
probably due.
* if the class cannot be found, the log should include the actual value of the
classname.
* normally I'd suggest using Configuration.getClass, but at that uses the
thread context classloader, it's probably not the right one
* what is needed then, if there's nothing already: check that the class can be
cast to a principal, and if not, again, fail with a meaningful message
> Can not find login module class for IBM due to hard codes
> ---------------------------------------------------------
>
> Key: HADOOP-15765
> URL: https://issues.apache.org/jira/browse/HADOOP-15765
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 3.0.3
> Reporter: Jianfei Jiang
> Priority: Major
> Attachments: HADOOP-15765_000.patch
>
>
> As the differences between various versions of IBM, the login module class is
> sometimes different. However, the class for specified jdk (no matter the
> version) is hard coded in Hadoop code. We have faced the error like following:
> *javax.security.auth.login.LoginException: unable to find LoginModule class:
> com.ibm.security.auth.module.LinuxLoginModule*
>
> Should we set the value as a config which can be set by users?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
