On Mon, 2009-02-02 at 00:40 +0100, Sidney Amani wrote: > Also I wonder how can the user provide his gCal username and password, > may be it can be stored in the mapiprofile?
I really don't think mapiprofile is the solution here. It is client-side only. What about a small database which entries would be similar to CN=username and using attributes such as gcal_username, gcal_password and gcal_enabled. This would provide the ability to have a different calendar for each user. Since the schema doesn't really matter, implementing such database using LDB can be done pretty quickly. Users may next control/update/enable/disable their information through a small python application or script (depending if it is meant to be local or remotely accessible) accessing the database. The script/service could authenticate users with their Exchange username/password and try to initiate a connection to the Exchange server to authenticate them. -- Julien Kerihuel [email protected] OpenChange Project Manager GPG Fingerprint: 0B55 783D A781 6329 108A B609 7EF6 FE11 A35F 1F79
signature.asc
Description: This is a digitally signed message part
_______________________________________________ devel mailing list [email protected] http://mailman.openchange.org/listinfo/devel
