directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre-Arnaud Marcelot (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DIRAPI-41) SASL connection information is not refreshed after a first SASL bind
Date Wed, 16 Feb 2011 14:28:57 GMT

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

Pierre-Arnaud Marcelot resolved DIRAPI-41.
------------------------------------------

    Resolution: Fixed

Fixed on both trunk and m1 branch.

http://svn.apache.org/viewvc?rev=1071263&view=rev
http://svn.apache.org/viewvc?rev=1071264&view=rev

> SASL connection information is not refreshed after a first SASL bind
> --------------------------------------------------------------------
>
>                 Key: DIRAPI-41
>                 URL: https://issues.apache.org/jira/browse/DIRAPI-41
>             Project: Directory Client API
>          Issue Type: Bug
>    Affects Versions: 1.0-M1
>            Reporter: Pierre-Arnaud Marcelot
>            Assignee: Pierre-Arnaud Marcelot
>             Fix For: 1.0-M2
>
>
> SASL connection information is not refreshed after a first SASL bind.
> Successive SASL binds reuse SASL information (user, credentials, realm, etc) from the
first bind method call, even if it is different in other bind method call. 

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message