It is able to register my CalDAV account, fetch all my calendars and synchronise regularly. Its problems have been fixed and now functions almost entirely.
#Caldav exchange client code#
Status code 405 returned (Not Allowed) for programmes connect to the server with the exact same credentials, no clue why Evolution fails. Unable to connect to 'Calendar': Cannot open calendar: Unexpected HTTP An error message is displayed that does not help much: Naturally, it is neither possible to create new events. Although easy to set up, the CalDAV connection fails repeatedly and the calendar contents are never displayed. It can be started with the "dummy" e-mail account.Įvolution comes with a good Help package that explains in detail the configuration of a CalDAV calendar.The most important hindrances to its usage on Ubuntu 14.04 have been fixed:
There are clear improvements, but it still is not possible to use a CalDAV calendar on Ubuntu. Ubuntu 16.04įollowing the advice of some commentators below, I gave another try to these programmes on Ubuntu 16.04. I was originally looking for one that works on 14.04, and now on 16.04. Java is a registered trademark of Oracle and/or its affiliates.I am looking for a functional CalDAV client for Ubuntu, preferably open source. For details, see the Google Developers Site Policies. They are available for a variety of programming languages check the page with libraries and samples for more details.Įxcept as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. Tip: The Google APIs client libraries can handle some of the authorization process for you. Information that Google supplies when you register your application (such as the client ID and the To request access using OAuth 2.0, your application needs the scope information, as well as Here's the OAuth 2.0 scope information for the Google Calendar API: Scope For detailed information about flows for various types of applications, see Google's OAuth 2.0 documentation. Some flows include additional steps, such as using refresh tokens to acquire new access tokens.
If the user approves, then Google gives your application a short-lived access token.Google displays a consent screen to the user, asking them to authorize your application to request some of their data.When your application needs access to user data, it asks Google for a particular scope of access.(If the API isn't listed in the API Console, then skip this step.) Activate the Google Calendar API in the Google API Console.Google then provides information you'll need later, such as a client ID and a When you create your application, you register it using the Google API Console.The following general process applies to all application types:
The details of the authorization process, or "flow," for OAuth 2.0 vary somewhat depending on what kind of application you're writing. Authorizing requests with OAuth 2.0Īll requests to the Google Calendar API must be authorized by an authenticated user. If your application uses Google Sign-In, some aspects of authorization are handled for you. No other authorization protocols are supported. Your application must use OAuth 2.0 to authorize requests. The token also identifies your application to Google. Every request your application sends to the Google Calendar API must include an authorization token.