You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jamie goodyear (Closed) (JIRA)" <ji...@apache.org> on 2012/01/11 18:02:41 UTC

[jira] [Closed] (KARAF-464) JAAS service configuration tracker does not unregister services or respond to service updates

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

Jamie goodyear closed KARAF-464.
--------------------------------

    
> JAAS service configuration tracker does not unregister services or respond to service updates
> ---------------------------------------------------------------------------------------------
>
>                 Key: KARAF-464
>                 URL: https://issues.apache.org/jira/browse/KARAF-464
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-core
>            Reporter: Kurt Westerfeld
>            Assignee: Ioannis Canellos
>             Fix For: 2.2.0
>
>
> The class org.apache.karaf.jaas.config.impl.OsgiConfiguration contains a java.util.List<JaasRealm> which is intended to track jaas realms added via blueprint via it's register/unregister pair using the whiteboard pattern.  This list is not mutated properly during unregister, since the list is not keyed by name or other id, and the passed in value during remove is a proxy.  Thus, after doing an "update" on a bundle that contains a jaas configuration, the list grows by one, but contains a stale service reference.
> When this occurs, a subsequent call to getAppConfigurationEntry() causes a runtime exception, "org.osgi.service.blueprint.container.ServiceUnavailableException".  No jaas-based authentication can happen after this.

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