Re: [Sieve-php-devel] Problem with Cyrus 2.2?

[Alexandros V. <av...@no...>]

On Wed, 2006-06-14 at 14:12 +0200, Hannes Muehleisen wrote:

> $sieve = new sieve($host, $port, $account, $admin_pass, $admin_username, 
> LOGIN');
> $sieve->sieve_login();
> 
> this is failing, however, if i go
> 
> $sieve = new sieve($host, $port, $account_username, $account_pass, '', 
> LOGIN');
> $sieve->sieve_login();
> 
> it works fine.

Can you check in case you force LOGIN authentication mechanism? It is
the only one that does not allow proxy auth (different authentication &
authorization ID).

In the meantime I've found that there are some inconsistencies in the
code with regard to authentication/authorization. At least the following
documentation in the comments is wrong: $auth represents the
authorization ID, however the authorization ID is the one that is used
as the proxy user, for instance putting the admin username in there.

---(snip) WRONG---
   * @param $user string is a super-user or proxy-user that has ACL
rights to
   * login on behalf of the $auth.
   *
   * @param $auth string is the authorized user identity for which the
SIEVE
   * scripts will be managed.
---(snip) WRONG---


As a temporary workaround, you can try swapping $account and
$admin_username and tell me if it works.

-- 
Alexandros Vellis
av...@no...