e Centrify module designed to work properly in
the Apache 2.2 authentication/authorisation architecture? That's a
question Centrify should be able to answer.
Regards,
Craig McQueen
Éibhear wrote:
Hi,
I hope you can help me.
I am using apache Apache/2.2.9 on Solaris 8 to control access t
Eric Covener wrote:
> On Mon, Jan 19, 2009 at 7:06 PM, Craig McQueen
> wrote:
>
>> Eric Covener wrote:
>>
>> On Mon, Dec 22, 2008 at 10:21 PM, Craig McQueen
>> wrote:
>>
>>
>> I'm trying to do LDAP authorisation with an Active Directory
I tried AuthLDAPRemoteUserIsDN. I can login by just entering a username.
It set REMOTE_USER to the full distinguished name, LDAP style:
CN=Craig McQueen,OU=Users,OU=MyDepartment,OU=All,DC=mycompany,DC=com,DC=au
That does enable the back-end to distinguish which domain the
authentication is on
Eric Covener wrote:
> On Mon, Dec 22, 2008 at 10:21 PM, Craig McQueen
> wrote:
>
>> I'm trying to do LDAP authorisation with an Active Directory server, and the
>> "Base DN" has Japanese characters in it. This should be no problem, but I
>> can't
odule
in properly sending the queries with UTF-8 content in the base DN. The
error.log file says "[ldap_search_ext_s() for user failed][No Such
Object]" which seems to indicate that the LDAP server isn't getting a
valid base DN.
Any insights on this?
Regards,
Craig McQueen
"other problem".
Regards,
Craig McQueen
Michele Mase' wrote:
Does the option 3 work changing the username from the form
domain\username into [EMAIL PROTECTED] (domain in fqd form i.e.
example.com <http://example.com>)?
Regards Michele
On Thu, Dec 11, 2008 at 9:12 AM, Craig
ers from
LOCALDOMAIN and users from REMOTEDOMAIN. If we had identical usernames
in the two domains, we wouldn't be able to separate them for authorisation.
So, we're currently stuck on all our options, for a variety of reasons.
Any thoughts on this?
Regards,
Craig McQueen
