Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Date: Tue, 8 May 2012 16:13:49 +0000 (UTC)
From: "David Jencks (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Message-ID: 
 <729941039.39400.1336493629156.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Resolved] (GERONIMO-5280) geronimo-jaspi jaspic provider
 won't work well under osgi
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/GERONIMO-5280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Jencks resolved GERONIMO-5280.
------------------------------------

    Resolution: Fixed

This is fixed at least in the jaspi component  2.0.0
                
> geronimo-jaspi jaspic provider won't work well under osgi
> ---------------------------------------------------------
>
>                 Key: GERONIMO-5280
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-5280
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: security
>    Affects Versions: 3.0
>            Reporter: David Jencks
>            Assignee: David Jencks
>             Fix For: 3.0
>
>
> The original geronimo-jaspi provider tried to use a "ClassLoaderLookup" to identify the classloader to use for loading auth modules.  I never actually got this to work well and it is pretty anti-osgi.  Instead we can use Rick's ProviderLocator from the specs.

--
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