On 17/06/13 2:34 PM, "Sebastien Goasguen" <run...@gmail.com> wrote:

>
>On Jun 17, 2013, at 4:54 AM, Ian Duffy <i...@ianduffy.ie> wrote:
>
>> Hi Sebastian,
>> 
>> I have updated the JIRA case for my project to add more steps so it is
>> like Nguyen's one.
>> 
>> Just after looking through JIRA, results are as follows:
>> 
>> (Resolved) CLOUDSTACK-2287 - Automation:LDAP: Appears to be solved.
>> tsp added tests for it.
>> 
>> (Resolved) CLOUDSTACK-1172 - Ldap enhancements: Marked of by abhi as
>>resolved.
>> 
>> (Blocked) CLOUDSTACK-1540 - LdapRemove within ui: Blocked due to
>> CLOUDSTACK-2168.
>> 
>> (Resolved) CLOUDSTACK-1495 - Change UI field name "bind username"
>> 
>> (Open) CLOUDSTACK-2168 - configured LDAP values not shown in UI.
>> Commenter says its a regression issues. When I tested this my values
>> disappeared and a message "No data to show" was given. Querying the
>> API directly still showed my LDAP configuration.
>> 
>> (Open) CLOUDSTACK-430 - Authentication should support multiple LDAP
>>servers.
>> 
>> (Resolved) CLOUDSTACK-1069 - Workaround for CS and LDAP users to login
>> simultaneously. Marked as unresolved, appears to be resolved based on
>> comments. Appears to no longer be an issue in 4.1 and 4.2 based on
>> comments on CLOUDSTACK-1930.
>> 
>> (Open) CLOUDSTACK-1062 - LDAP integration with ACS user management,
>> detailed at 
>>https://cwiki.apache.org/confluence/display/CLOUDSTACK/ACS+integration+wi
>>th+User+LDAP+base
>> 
>> (Open) Cloudstack-1213 - LDAP SSL auth failed to setup. On first look
>> and reading of the error message It appears to be a user issue with
>> the trustedstore certificate not existing.
>> 
>> (Fixed) Cloudstack-1142 - due to "%" being illegal character. Marked
>> as big fixed.
>> 
>> (Fixed) CLOUDSTACK-1398 - Failed to update job status. Marked fixed.
>> 
>> (Fixed) CLOUDSTACK-1494 - Showing wrong warning messages. Markd as
>>Fixed.
>
>Ian thanks for this,
>
>Where it makes sense, feel free to comment and test.
>
>If some of those open bugs fit into your project plan, make sure to link
>to those jira bugs
>If you think you can fix them, feel free to claim the bugs and assign
>them to you.
>
>-Sebastien
>
>
In case some of these bugs do not make sense, do discuss these with me.

-abhi
>


Reply via email to