You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, if the authentication (or authorization) for a calendar stops working (examples: a) the CalDAV password has changed; b) for Outlook 365, the client PC was offline for over one month, invalidating the OAuth refresh token), the user has to repeat the entire configuration process.
Instead, calendar providers should throw a specific exception that indicates that the authz/authn has become invalid, allowing the user to re-authenticate. A set of sensibly-chosen parameters should be re-used (e.g. O365 Client ID, or CalDAV username), offering them as default values, but still allowing the user to change them.
When the user then runs the configure command again, they are allowed to fix only the calendar authentication.
The text was updated successfully, but these errors were encountered:
At the moment, if the authentication (or authorization) for a calendar stops working (examples: a) the CalDAV password has changed; b) for Outlook 365, the client PC was offline for over one month, invalidating the OAuth refresh token), the user has to repeat the entire configuration process.
Instead, calendar providers should throw a specific exception that indicates that the authz/authn has become invalid, allowing the user to re-authenticate. A set of sensibly-chosen parameters should be re-used (e.g. O365 Client ID, or CalDAV username), offering them as default values, but still allowing the user to change them.
When the user then runs the
configure
command again, they are allowed to fix only the calendar authentication.The text was updated successfully, but these errors were encountered: