qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Ritchie (JIRA)" <qpid-...@incubator.apache.org>
Subject [jira] Commented: (QPID-1390) Authentication Manager does not correctly unregister custom SASL providers on shutdown
Date Fri, 24 Oct 2008 16:05:44 GMT

    [ https://issues.apache.org/jira/browse/QPID-1390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12642482#action_12642482
] 

Martin Ritchie commented on QPID-1390:
--------------------------------------

AuthenticationManager updated to have close method.
ApplicationRegistry has been updated with commented out methods highlighting the missing manager
closes still to be implemented as JIRA'd in QPID-1399

> Authentication Manager does not correctly unregister custom SASL providers on shutdown
> --------------------------------------------------------------------------------------
>
>                 Key: QPID-1390
>                 URL: https://issues.apache.org/jira/browse/QPID-1390
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Broker
>    Affects Versions: M3
>            Reporter: Martin Ritchie
>            Assignee: Martin Ritchie
>             Fix For: M4
>
>
> Summary:
> The AuthenticationManger (PrincipalDatabaseAuthenticationManager) registers custom SASL
servers on startup. However, on shutdown of the ApplicationRegistry it does not remove these.
This could be a cause of the curious SASL related failures in SimpleACLTest.
> On ApplicationRegistry close all the managers should get a notification so that they
may perform any additional clean up.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message