You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Brian Federle (JIRA)" <ji...@apache.org> on 2013/07/12 20:53:53 UTC

[jira] [Updated] (CLOUDSTACK-1637) LDAP:UI related issues

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

Brian Federle updated CLOUDSTACK-1637:
--------------------------------------

    Assignee:     (was: Pranav Saxena)
    
> LDAP:UI related issues
> ----------------------
>
>                 Key: CLOUDSTACK-1637
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1637
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>            Reporter: sadhu suresh
>             Fix For: 4.2.0
>
>
> case 1:Clear the port number value when we check the ssl check box.
> when we check the SSL ,Port value shows 389 but required value is 636.
> expected result: when ssl enabled ,clear the default389 value from port field and  restrict the user to enter value.so that end user enter proper value(in case of AD its 636)
> Case2: no automatic page refresh when we configured new LDAP,i.e we are seeing both records(current and previous configuration details) till you refresh the page manually.
> Steps:
> 1.configured the LDAP from UI
> 2.again congured the another LDAP
> 3.check the UI
> Actual result:
> able to see both previous and current LDAP configuration details till you refresh the page manually. once you fresh it showing the correct details.
> Expected results:
> when we add new  LDAP configuration  details,previous details should be overwritten with current value and same thing should be reflected in UI automatically instead of showing both details till you refresh the page.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira