Tickets :: Comment on [#14592] Microsoft EWS

* Your Email Address
* Spam protection	Enter the letters below: __..__ .__..__ .__. (__ \| \[__][ __[__] .__)\|__/\| \|[_./\| \|
Comment	>>> What would that get us that the current Horde API doesn't provide already? >> >> Today I discovered that it is impossible to access shared calendars >> or address books using EAS. Apparently EAS doesn't do permissions - >> so it doesn't expose shared calendars or address books. I use the >> alternately the Horde native interface and Thunderbird to access >> Horde as a back-end (using TBSync). For the reason above I can only >> access the user's own calendar(s) or address book(s) - and not others >> which they have been given access to. This would be a limitation for >> all other ActiveSyns/EAS clients - such as mobile phone clients or >> other calendaring software connecting to Horde. >> >> So that seems to me like a significant limitation. As far as I >> understand, EWS implements permissions, so software using it can >> expose shared calendars and address books. > > That's not 100% true. Yes, EAS doesn't support permissions, but Horde > will synchronize any shared that the user has write access to. Yes > still a limitation, but it is extremely unlikely we will implement > EWS.
Attachment
Watch this ticket