summaryrefslogtreecommitdiff
path: root/src/modules
Commit message (Collapse)AuthorAgeFilesLines
* M!117 - Replace GTimeVal by GDateTime or int64Corentin Noël2023-03-201-3/+4
| | | | | | We need to use something else to be Y2038-proof. Closes https://gitlab.gnome.org/GNOME/evolution-data-server/-/merge_requests/117
* Parse URI strings into GUri in a relaxed modeMilan Crha2023-01-311-1/+1
| | | | | | | | | The provided URI strings can be sometimes incorrectly constructed, like an `@` in the user name part not being encoded, which causes incorrect parse into the GUri without the relaxed mode (it stops parsing the user information on the first `@`, not the second), leading into an incorrect host name. Related to https://gitlab.gnome.org/GNOME/evolution/-/issues/2228
* Replace GcrCertificateWidget with libedataserverui's ECertificateWidgetMilan Crha2022-08-114-102/+15
| | | | | | The GcrCertificateWidget will be removed, thus use the one provided by the libedataserverui instead. It helps to limit spread of the GCR in the code.
* Replace libgdata dependency with built-in functionsMilan Crha2022-07-072-55/+35
| | | | | Since the new Google Data Tasks API functions being added, the libgdata dependency can be dropped and replaced with it.
* M!80 - Provide libedataserverui for gtk4Milan Crha2022-06-223-9/+37
| | | | Closes https://gitlab.gnome.org/GNOME/evolution-data-server/-/merge_requests/80
* M!85 - Port to libsoup3Milan Crha2022-06-222-91/+102
| | | | Closes https://gitlab.gnome.org/GNOME/evolution-data-server/-/merge_requests/85
* GOA module: Prevent ESource removal on D-Bus reconnect or registry reloadMilan Crha2022-05-181-8/+17
| | | | | | | | | | | | The GOA module is persistent between evolution-source-registry reloads, which means its `goa_to_eds` hash table could be left filled when the gnome_online_accounts_populate_accounts_table() is called, thus it could remove existing ESource-s, because it looked like the GOA account ID is used by a different ESource. The gnome_online_accounts_populate_accounts_table() is called when establishing a connection to the goa-daemon, which can also happen during runtime.
* goa-ews: Handle certificate errors during autodiscoverMilan Crha2022-05-181-0/+31
| | | | | | If there was any certificate error during autodiscover on the GOA side, the user explicitly ignored the error when creating the account, thus the repeated autodiscover on the eds side can also ignore it.
* I#379 - OAuth2: Option to use browser of choice for authenticationMilan Crha2022-04-071-4/+1
| | | | Closes https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/379
* secret-monitor: Turn runtime warnings into debug printsMilan Crha2021-11-221-2/+2
| | | | | | | | No need to write failures from this module into the journal log, because these failures are not critical, they only mean that some credentials could not be deleted due to certain error. The errors can still be shown when the evolution-source-registry debugging is turned on (when it's run with ESR_DEBUG=1).
* evo-I#1698 - Bundle legacy icons removed from adwaita-icon-themeMilan Crha2021-11-182-1/+15
| | | | Related to https://gitlab.gnome.org/GNOME/evolution/-/issues/1698
* Addressbook: Switch from GData Contacts API to CardDAV API for Google booksMilan Crha2021-06-031-129/+12
| | | | | | | | | The GData Contacts API is going to be shut down [1], thus move to the CardDAV API, which the Google server supports too. [1] https://developers.google.com/contacts/v3/announcement Related to https://gitlab.gnome.org/GNOME/libgdata/-/issues/42
* gnome_online_accounts_create_client_cb: Prefer g_clear_object()Milan Crha2021-05-061-2/+1
| | | | | | The cancellable could be NULL, in which case a runtime warning is printed on the console. There's the g_clear_object(), which helps in this situation.
* I#317 - Add OAuth2 for Yahoo! accountsMilan Crha2021-03-191-3/+3
| | | | Closes https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/317
* M!44 - Typo 'the the ' -> 'the 'Дилян Палаузов2020-10-011-1/+1
| | | | Closes https://gitlab.gnome.org/GNOME/evolution-data-server/-/merge_requests/44
* Minor white-space correctionMilan Crha2020-08-281-5/+5
|
* I#208 - Avoid race condition when refreshing collection backendMilan Crha2020-08-281-1/+4
| | | | Closes https://gitlab.gnome.org/GNOME/evolution-data-server/-/issues/208
* I#198 - goa: Doesn't set ESourceAuthentication::is-external properlyMilan Crha2020-03-051-6/+3
| | | | Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/198
* I#192 - Collection accounts: Do not suddenly enable disabled sub-sourcesMilan Crha2020-02-191-1/+0
| | | | Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/192
* M!33 - ESourceAuthentication: Add is-external propertyCorentin Noël2019-09-093-13/+29
| | | | | | ...and use it instead of checking UOA or GOA extensions existence Closes https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/33
* M!32 - Replace deprecated 'g_type_class_add_private'Pablo Barciela2019-09-092-19/+12
| | | | Closes https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/32
* Fix two memory leaksMilan Crha2019-08-161-2/+8
|
* GOA module: Run EWS autodiscovery asynchronouslyMilan Crha2019-08-151-41/+55
| | | | | | | | | The autodiscovery does network I/O, which means it can block. The place where it is invoked is called from the main thread of the source registry process, which means, in case the server is unresponsive for whatever reason, the blocking call blocks also the source registry, making it unresponsive until the autodiscovery timeouts or others eds. To fix this, run the autodiscovery asynchronously instead.
* M!18 - Prefer g_string_append_c() over g_string_append()Дилян Палаузов2019-07-081-1/+1
| | | | | | Likewise for g_string_prepend_c() and g_string_prepend(). Closes https://gitlab.gnome.org/GNOME/evolution-data-server/merge_requests/18
* [Flatpak] Save passwords in libsecret with the same prefix as used by D-Bus ↵Milan Crha2018-12-031-2/+8
| | | | | | | | | | | services As the passwords are saved in the host system, the eds-origin key cannot use the same value as the host system, because otherwise the secret-monitor module of evolution-source-registry would delete the password, because the ESource is unknown to it. Similarly the other way around, the inner (in Flatpak) source registry would delete system passwords, because those ESource-s are unknown to it.
* I#51 - [Gmail] Change from OAuth2 to other authentication doesn't stickMilan Crha2018-11-011-17/+59
| | | | Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/51
* I#34 - Remove Ubuntu Online Accounts from masterMilan Crha2018-09-2419-2827/+0
| | | | | | It had been moved to https://gitlab.com/accounts-sso/evolution-data-server-signon Closes https://gitlab.gnome.org/GNOME/evolution-data-server/issues/34
* Address two Clang warningsMilan Crha2018-09-031-0/+1
|
* [module-secret-monitor] Correct runtime warning from ↵Milan Crha2018-05-181-7/+6
| | | | | | | | | | secret_service_search_sync() The evolution-source-registry console could contain a runtime warning: WARNING **: secret_service_search_sync: must specify at least one attribute to match which was due to calling secret_service_search_sync() with an empty hash table of attributes. Adding an 'eds-origin' attribute to the keys and search for it helps to make the module do what it was supposed to do.
* Introduce e_util_debug_print() for consistent debug print formMilan Crha2018-04-061-24/+1
|
* Bug 794879 - GOA-configured Google account has set wrong authentication methodMilan Crha2018-04-061-13/+27
|
* Bug 793963 - Add debugging for GOA accountsMilan Crha2018-03-141-10/+125
|
* Change how built-in OAuth2 authentication worksMilan Crha2018-01-224-18/+350
| | | | | | | | This change allows easier extending of built-in OAuth2 authentications with minimal code "duplication". A CMake option ENABLE_GOOGLE_AUTH had been renamed to ENABLE_OAUTH2 to reflect this extensibility as well.
* Merge duplicated code around EGDataOAuth2AuthorizerMilan Crha2017-11-214-486/+7
|
* [OAuth2] Enhance how expired or invalid access tokens are handledMilan Crha2017-11-211-9/+42
| | | | | | | | | | | | With respect of ESoupAuthBearer (used mainly with CalDAV), the missing implementation of the e_soup_auth_bearer_update() could cause repeated requests with the invalid access token, which had been eventually aborted after many tries by libsoup with a runtime warning: "SoupMessage <pointer> stuck in infinite loop?" The change makes the access token expired in such case, which stops the cycle early and doesn't increase the error counter on the server. The GData authorizers didn't consider expiration time at all.
* [google-backend] Limit for what sources authentication method is changedMilan Crha2017-11-071-16/+40
| | | | | | | The Google backend module unconditionally changed authentication method of all but the mail sources, even when those didn't connect to a Google server, which is certainly wrong, thus this change extends the check from the mail sources to other types as well.
* Misleading error for Google collection account without Calendar partMilan Crha2017-09-201-0/+2
| | | | | | | | | When a Google collection account had not enabled Calendar part, a misleading error about failed connection for the account with "Unknown error" detailed description could show up. The reason was that the Google backend didn't even try to connect, due to the disabled Calendar part, but it reported error, even without actual error message (hence the "Unknown error" text).
* [EGoaPasswordBased] Reuse GoaClient object between password lookup callsMilan Crha2017-09-191-2/+75
| | | | | | | The GoaClient object had been created whenever a password lookup had been initiated for the EGoaPasswordBased object, which could also mean having several such objects in memory at one time, even it's not necessary.
* Ignore "timed out" error from goa_account_call_ensure_credentials_sync()Milan Crha2017-09-151-5/+10
| | | | | | It can be that the server is very slow, then the timeout on the D-Bus call can be reached sooner than the server responds, thus let's ignore the error and continue to get the stored password from GOA.
* Add calendar and contacts URLs into ESourceCollection extensionMilan Crha2017-08-041-7/+14
| | | | | These can be used similarly as those in ESourceGoa extension. Currently only "webdav" collection backend uses these properties.
* Rename owncloud-backend module to webdav-backendMilan Crha2017-08-024-38/+38
| | | | | | There had been nothing specific about ownCloud in the module, thus make it a generic WebDAV module, which can be reused when needed. A migration code for the change had been added as well.
* Introduce EWebDAVCollectionBackend to be used for WebDAV-discovered collectionsMilan Crha2017-07-213-795/+84
| | | | | | Any server providing CalDAV/CardDAV interfaces to access the calendars, memo lists, task lists and address books may derive from this new object and avoid code duplication.
* Bug 783385 - Prefer SSL over STARTTLS for mail when both are set in GOAMilan Crha2017-06-122-12/+8
|
* Remove forgotten debug printMilan Crha2017-05-091-1/+0
|
* Bug 781543 - Provide all Google Task listsMilan Crha2017-04-204-101/+601
|
* Bug 778775 - Add carddav scope to google-contacts.service for Ubuntu online ↵Khurshid Alam2017-02-171-1/+1
| | | | accounts
* Bug 777207 - Allow e-mail address change for GOA configured accountsMilan Crha2017-01-171-21/+112
|
* Bug 774841 - [EWebDAVDiscover] One part failure caused credentials rejectMilan Crha2016-12-012-0/+4
|
* Bug 774331 - Use Unicode in translatable stringsPiotr Drąg2016-11-237-13/+13
| | | | See https://developer.gnome.org/hig/stable/typography.html
* Bug 774103 - GOA mail account doesn't inherit GoaMail::nameMilan Crha2016-11-101-3/+16
|
View Lorry Controller Status