Karaf
  1. Karaf
  2. KARAF-806

ProxyLoginModule should actually be on the bootclasspath classpath right?

    Details

    • Type: Question Question
    • Status: Closed
    • Priority: Trivial Trivial
    • Resolution: Fixed
    • Affects Version/s: 2.2.2
    • Fix Version/s: 2.2.6, 3.0.0
    • Component/s: karaf-documentation
    • Labels:
      None

      Description

      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.

        Activity

          People

          • Assignee:
            Unassigned
            Reporter:
            Todor Boev
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development