On Tue, 2007-02-13 at 08:09 +0100, Axel Westerhold wrote:
One comment on a nice feature I would like to have but still considering for
security reasons:
When an ICAP Server requieres auth for user mapping to rules/policies you
sometimes run into a problem with sources with can't auth or
On Mon, 2007-02-12 at 08:38 +0100, Axel Westerhold wrote:
Well, the syntax you are proposing is somewhat limited.
Here are my comments:
1.) cn=%u assumes that the used username equals the assigned CN which is
most of the time wrong. Normally the UID (or in AD the samaccountname) is
used
Hi Alex,
Am 13.02.2007 6:03 Uhr schrieb Alex Rousskov unter
[EMAIL PROTECTED]:
On Mon, 2007-02-12 at 08:38 +0100, Axel Westerhold wrote:
Well, the syntax you are proposing is somewhat limited.
Here are my comments:
1.) cn=%u assumes that the used username equals the assigned CN
Good morning,
Well, the syntax you are proposing is somewhat limited.
Here are my comments:
1.) cn=%u assumes that the used username equals the assigned CN which is
most of the time wrong. Normally the UID (or in AD the samaccountname) is
used for authentication. This will lead to a failure
Hello,
I can't remember. What was the decided path for what was once the
icap_auth_scheme? I recall there was some concern about my suggestion of
having the ability to use ldap://hostname/cn=%u,dc=%d,dc=name,dc=int
but I don't remember what the outcome was.
_J
On Fri, 2007-02-09 at 15:55 -0500, Jeremy Hall wrote:
Hello,
I can't remember. What was the decided path for what was once the
icap_auth_scheme? I recall there was some concern about my suggestion of
having the ability to use ldap://hostname/cn=%u,dc=%d,dc=name,dc=int
but I don't
