You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (Resolved JIRA)" <ji...@apache.org> on 2012/03/26 09:02:27 UTC
[jira] [Resolved] (KARAF-806) ProxyLoginModule should actually be
on the bootclasspath classpath right?
[ https://issues.apache.org/jira/browse/KARAF-806?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré resolved KARAF-806.
----------------------------------------
Resolution: Fixed
After digging, it should be in the boot classloader.
> ProxyLoginModule should actually be on the bootclasspath classpath right?
> -------------------------------------------------------------------------
>
> Key: KARAF-806
> URL: https://issues.apache.org/jira/browse/KARAF-806
> Project: Karaf
> Issue Type: Question
> Components: karaf-documentation
> Affects Versions: 2.2.2
> Reporter: Todor Boev
> Priority: Trivial
> Fix For: 2.2.6, 3.0.0
>
>
> In Developers Guide, Security Framework, Architecture (section)
> http://karaf.apache.org/manual/2.2.2/developers-guide/security-framework.html
> It is mentioned that ProxyLoginModule must be "available from the system classloader". This does not seem correct. The LoginContext class calls Class.forName(<module class>, true, <context class loader>) to load the login module classes. When the context loader is null Class.forName() delegates to the loader of the current class, which in the case of LoginContext is the boot loader. So if we have ProxyLoginModule on the system classpath it will be bypassed.
> In equinox we can get away with this because equinox sets a context class loader of it's own, which delegates to the system loader. I suspect on Felix this will not work.
--
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