Re: [evolution-patches] patch for addressbook.c



i was using a mime-type sort of approach to auth types
(ldap/simple-binddn, ldap/simple-email, sasl/DIGEST, etc), so maybe
"plain/password" instead of "Password"?

also is there some way we can avoid putting knowledge of a particular
uri scheme in the front end?  The fact that there's ldap specific code
in the front end is something we need to eventually address, but we
shouldn't be adding more..  Can we get around this by passing the
book_name as an ESource property instead of as part of the uri?

Chris

On Sun, 2004-04-11 at 17:53 +0530, Sivaiah N wrote:
> Hi,
> The attached patch has the following changes 
> 1) in addressbook_authenicate function auth value is compared with one
> more type auth method "Password"  defined for  groupwise.
> 2) Groupwise uris has the book name as part of it.The uri format is
> groupwise://server:port/soap?book_name. In functions
> addressbook_authenicate and load_source_auth_cb functions the book_name
> part is removed from the uri before passing it to e_password_* apis so
> that user need to enter the password just once instead of for each book.
> 
> Thanks,
> Sivaiah



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]