Brandon G wrote:
> Rich Megginson wrote:
>> When you first log in to the console, and you type in your ID, the
>> directory server has no credentials, and has to perform an anonymous
>> search for uid=youruid to find your BIND DN. This is the same as when
>> you log in to the operating system -
Rich Megginson wrote:
When you first log in to the console, and you type in your ID, the
directory server has no credentials, and has to perform an anonymous
search for uid=youruid to find your BIND DN. This is the same as when
you log in to the operating system - pam has to do a search like
Gerrard Geldenhuis wrote:
What's not necessary? Note that the admin server and directory server
have separate cert databases. Also note that the NSS crypto team is
working towards a unified system-wide cert db.
>>> That could have been more clear, I meant that a
ugust 2010 16:00
>> To: 389-us...@lists.fedoraproject.org
>> Subject: [389-users] Console breaks when enabling no anoymous binding
>>
>> Hi
>> If I set
>> nsslapd-allow-anonymous-access: off
>> I am not able to login to the 389-console. I can remedy this by checking the
t;Subject: [389-users] Console breaks when enabling no anoymous binding
>
>Hi
>If I set
>nsslapd-allow-anonymous-access: off
>I am not able to login to the 389-console. I can remedy this by checking the
>checkbox "Use SSL in Console" in the Encryption tab on the Directory Se
Gerrard Geldenhuis wrote:
> Hi
> If I set
> nsslapd-allow-anonymous-access: off
> I am not able to login to the 389-console. I can remedy this by checking the
> checkbox "Use SSL in Console" in the Encryption tab on the Directory Server
> console. This seems a strange solution to the problem. Wh
Hi
If I set
nsslapd-allow-anonymous-access: off
I am not able to login to the 389-console. I can remedy this by checking the
checkbox "Use SSL in Console" in the Encryption tab on the Directory Server
console. This seems a strange solution to the problem. Why would disabing
anonymous access bre
