Ian Forde created CLOUDSTACK-8046:
-------------------------------------
Summary: should listLdapAccounts perform a case-insensitive match
against existing CS accounts?
Key: CLOUDSTACK-8046
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8046
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: API
Affects Versions: 4.3.1
Reporter: Ian Forde
Priority: Minor
When using the listLdapUsers API call with Active Directory servers defined,
the list of undefined users is returned from AD and can include users with
mixed-case usernames, where their fully-lowercased versions already exist in
CS. Should this check be case-insensitive, as we can't add those users anyway?
Example:
cloudmonkey api listLdapUsers listtype=new filter=username,domain
If we have a Cloudstack user named, "bjones", and there's one in AD entitled,
"Bjones", the above command will continue to return "Bjones" as an unadded
user, even though I don't believe that "Bjones" can be added at this point.
I'm honestly not sure if this (ignoring case) should be a mandatory thing or an
option, though it's definitely a corner case...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
