[asterisk-bugs] [JIRA] (ASTERISK-30106) res_calendar_icalendar: Microsoft online ICS calendars no longer work

[N A (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-30106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=259530#comment-259530 ] 

N A commented on ASTERISK-30106:
--------------------------------

It's also worth noting that apparently Basic authentication was discontinued by Microsoft on October 13, 2020: https://techcommunity.microsoft.com/t5/exchange-team-blog/upcoming-changes-to-exchange-web-services-ews-api-for-office-365/ba-p/608055

It seems that res_calendar_ews only supports basic authentication and not OAuth, so I believe that means res_calendar_ews is completely unusable at this point. I don't agree with Microsoft or other vendors phasing out basic auth, but if that's the reality, these applications either need to be updated to follow suit or... deprecated, which wouldn't be ideal either.

So, on-prem Exchange connections would still work I imagine but I think users with Microsoft accounts may be SOL at the moment...

> res_calendar_icalendar: Microsoft online ICS calendars no longer work
> ---------------------------------------------------------------------
>
>                 Key: ASTERISK-30106
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30106
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Resources/res_calendar_icalendar
>    Affects Versions: 18.12.0
>            Reporter: N A
>
> A few days ago, outlook.com shared ICS calendars seemed to stop working, for no apparent reason.
> Every 10 minutes, I get these warnings in the CLI:
> {noformat}
> [Jun 12 08:54:39] WARNING[564844]: res_calendar_icalendar.c:151 fetch_icalendar: Unable to retrieve iCalendar 'REDACTED' from 'https://REDACTED/calendar.ics': 400
> [Jun 12 08:54:39] WARNING[564844]: res_calendar_icalendar.c:478 ical_load_calendar: Unable to parse iCalendar 'REDACTED'
> [Jun 12 08:54:39] ERROR[564844]: res_calendar_icalendar.c:366 icalendar_update_events: The iCalendar has not been parsed!
> [Jun 12 08:54:39] WARNING[564842]: res_calendar_icalendar.c:151 fetch_icalendar: Unable to retrieve iCalendar 'REDACTED' from 'https://REDACTED/calendar.ics': 400
> [Jun 12 08:54:39] WARNING[564842]: res_calendar_icalendar.c:478 ical_load_calendar: Unable to parse iCalendar 'REDACTED'
> [Jun 12 08:54:39] ERROR[564842]: res_calendar_icalendar.c:366 icalendar_update_events: The iCalendar has not been parsed!
> [Jun 12 08:54:39] WARNING[564843]: res_calendar_icalendar.c:151 fetch_icalendar: Unable to retrieve iCalendar 'REDACTED' from 'https://REDACTED/calendar.ics': 400
> [Jun 12 08:54:39] WARNING[564843]: res_calendar_icalendar.c:478 ical_load_calendar: Unable to parse iCalendar 'REDACTED'
> [Jun 12 08:54:39] ERROR[564843]: res_calendar_icalendar.c:366 icalendar_update_events: The iCalendar has not been parsed!
> {noformat}
> As a result, calendaring has completely broken in Asterisk for me.
> Importantly:
> - This happens with all calendars for Outlook.com, and in multiple Microsoft accounts, so it's not an account issue.
> - Other ICS links work fine without triggering these warnings
> - Outlook.com shared ICS calendars work fine in other calendaring programs, e.g. mail clients
> So the problem is both specific to the Office 365 ICS format as well as Asterisk since both are required to trigger the problem. Even if Microsoft changed something, it seems to work fine in other applications so there seems to be some lack of support given the 400 Bad Request errors.
> Tested with both Debian 10 and Debian 11, and Asterisk 18.9 and Asterisk 18.12.



--
This message was sent by Atlassian JIRA
(v6.2#6252)