[
https://issues.apache.org/jira/browse/OAK-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chetan Mehrotra updated OAK-256:
--------------------------------
Attachment: OAK-256-tccl-switch.patch
Patch to switch TCCL while creating LoginContext. Note that LoginContext stores
the TCCL as part of creation itself. If required the TCCL switch can be done
ContentRepository.login method also
> JAAS Authentication failing in OSGi env due to classloading issue
> -----------------------------------------------------------------
>
> Key: OAK-256
> URL: https://issues.apache.org/jira/browse/OAK-256
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Affects Versions: 0.5
> Reporter: Chetan Mehrotra
> Labels: osgi, sling
> Attachments: OAK-256-tccl-switch.patch
>
>
> At times Repository login fails because the LoginModule cannot be
> instantiated
> {noformat}
> Caused by: javax.jcr.LoginException: unable to find LoginModule class:
> org.apache.jackrabbit.oak.security.authentication.LoginModuleImpl
> at
> org.apache.jackrabbit.oak.jcr.RepositoryImpl.login(RepositoryImpl.java:139)
> at
> org.apache.jackrabbit.oak.jcr.SessionImpl.impersonate(SessionImpl.java:114)
> at
> org.apache.sling.jcr.base.SessionProxyHandler$SessionProxyInvocationHandler.invoke(SessionProxyHandler.java:101)
> at $Proxy9.impersonate(Unknown Source)
> at
> org.apache.sling.jcr.davex.impl.servlets.SlingDavExServlet$1.getLongLivedSession(SlingDavExServlet.java:206)
> {noformat}
> As a fix LoginContextProviderImpl should switch the Thread's context
> classloader (TCCL) to oak-jcr bundle's classloader so that required
> loginmodule class can be instantiated
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
