You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Ian Forde <if...@marketo.com> on 2014/12/06 01:40:43 UTC
4.3.1 API issue with importing LDAP users
I’ve got a bash script performing an API call (in my case, via cloudmonkey) as follows:
cloudmonkey api listLdapUsers listtype=new display=default filter=username,domain
(note that we’re using Active Directory)
There’s at least one user in AD defined with a capital letter in front. Example: “Bjones" rather than "bjones". Now given that we have a user in CS named bjones, Bjones shouldn’t show up in the output from the above command, but it does.
Is this supposed to happen or is the listLdapUsers supposed to perform a case-insensitive match against currently-defined Cloudstack user accounts?
Thanks,
-Ian
Re: 4.3.1 API issue with importing LDAP users
Posted by Ian Forde <if...@marketo.com>.
Created. CLOUDSTACK-8046. I¹d also like to point out that you may want
to add ³LDAP² to the Components menu in JiraŠ
-I
On 12/6/14, 6:32 AM, "Ian Duffy" <ia...@ianduffy.ie> wrote:
>Hi.
>
>Haven't looked at the code but it sounds like a casing issue.
>
>AD is case aware but not case sensitive. I'm unsure of the top of my head
>what POSIX LDAP is.
>
>Probably best if we change to suit ADs case awareness. i.e. copy across as
>same casing and allow login from any case variation.
>
>Can you open a jira ticket?
>
>Thanks,
>Ian
>On 6 Dec 2014 01:48, "ilya musayev" <il...@gmail.com> wrote:
>
>> Hi Ian,
>>
>> This is probably better suited for Dev list, Ian Duffy has done alot of
>> work on LDAP and CloudStack, he is cc'd to this thread. Perhaps he can
>>shed
>> some light.
>>
>> Regards
>> ilya
>>
>> On 12/5/14, 4:40 PM, Ian Forde wrote:
>>
>>> I¹ve got a bash script performing an API call (in my case, via
>>> cloudmonkey) as follows:
>>>
>>> cloudmonkey api listLdapUsers listtype=new display=default
>>> filter=username,domain
>>>
>>> (note that we¹re using Active Directory)
>>>
>>> There¹s at least one user in AD defined with a capital letter in front.
>>> Example: ³Bjones" rather than "bjones". Now given that we have a
>>>user in
>>> CS named bjones, Bjones shouldn¹t show up in the output from the above
>>> command, but it does.
>>>
>>> Is this supposed to happen or is the listLdapUsers supposed to perform
>>>a
>>> case-insensitive match against currently-defined Cloudstack user
>>>accounts?
>>>
>>> Thanks,
>>> -Ian
>>>
>>>
>>
Re: 4.3.1 API issue with importing LDAP users
Posted by Ian Duffy <ia...@ianduffy.ie>.
Hi.
Haven't looked at the code but it sounds like a casing issue.
AD is case aware but not case sensitive. I'm unsure of the top of my head
what POSIX LDAP is.
Probably best if we change to suit ADs case awareness. i.e. copy across as
same casing and allow login from any case variation.
Can you open a jira ticket?
Thanks,
Ian
On 6 Dec 2014 01:48, "ilya musayev" <il...@gmail.com> wrote:
> Hi Ian,
>
> This is probably better suited for Dev list, Ian Duffy has done alot of
> work on LDAP and CloudStack, he is cc'd to this thread. Perhaps he can shed
> some light.
>
> Regards
> ilya
>
> On 12/5/14, 4:40 PM, Ian Forde wrote:
>
>> I’ve got a bash script performing an API call (in my case, via
>> cloudmonkey) as follows:
>>
>> cloudmonkey api listLdapUsers listtype=new display=default
>> filter=username,domain
>>
>> (note that we’re using Active Directory)
>>
>> There’s at least one user in AD defined with a capital letter in front.
>> Example: “Bjones" rather than "bjones". Now given that we have a user in
>> CS named bjones, Bjones shouldn’t show up in the output from the above
>> command, but it does.
>>
>> Is this supposed to happen or is the listLdapUsers supposed to perform a
>> case-insensitive match against currently-defined Cloudstack user accounts?
>>
>> Thanks,
>> -Ian
>>
>>
>
Re: 4.3.1 API issue with importing LDAP users
Posted by ilya musayev <il...@gmail.com>.
Hi Ian,
This is probably better suited for Dev list, Ian Duffy has done alot of
work on LDAP and CloudStack, he is cc'd to this thread. Perhaps he can
shed some light.
Regards
ilya
On 12/5/14, 4:40 PM, Ian Forde wrote:
> I’ve got a bash script performing an API call (in my case, via cloudmonkey) as follows:
>
> cloudmonkey api listLdapUsers listtype=new display=default filter=username,domain
>
> (note that we’re using Active Directory)
>
> There’s at least one user in AD defined with a capital letter in front. Example: “Bjones" rather than "bjones". Now given that we have a user in CS named bjones, Bjones shouldn’t show up in the output from the above command, but it does.
>
> Is this supposed to happen or is the listLdapUsers supposed to perform a case-insensitive match against currently-defined Cloudstack user accounts?
>
> Thanks,
> -Ian
>