[SRU] Add carddav scope to google-contacts.service
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
evolution-data-server (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Yakkety |
Triaged
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Now that Yakkety is going to have eds 3.22.6 and as upstream released the fix for 3.22.6, it automatically became eligible for backporting to Yakkety.
[Test case]
After update, users should be able to sync contacts with google carddav server via syncevolution.
[Regression Potential]
None.
[Original Description]
It seems google-
For example, running following command:
'''
SYNCEVOLUTION_
loglevel=2 backend=carddav username=
syncURL=https:/
'''
gives following error:
“𝗣𝗥𝗢𝗣𝗙𝗜𝗡𝗗: 𝗡𝗲𝗼𝗻 𝗲𝗿𝗿𝗼𝗿 𝗰𝗼𝗱𝗲 𝟭: 𝟰𝟬𝟯 𝗙𝗼𝗿𝗯𝗶𝗱𝗱𝗲𝗻, 𝗺𝘂𝘀𝘁 𝗻𝗼𝘁 𝗿𝗲𝘁𝗿𝘆”
Adding the carddav scope solves the issue. 'https:/
evolution-
Patch:
--- a/modules/
+++ b/modules/
@@ -17,7 +17,7 @@
<setting name="RedirectUri">https:/
<setting name="ClientId"
<setting name="ClientSec
- <setting type="as" name="Scope">['https:/
+ <setting type="as" name="Scope">['https:/
</group>
</group>
</group>
Note:
1. Ubuntu already enabled carddav in google developer console (lp:1433943)
2. It requires to grant access twice; one for UOA and one for Evolution (server side). Then only it works (https:/
summary: |
- Add carddav scope to google-contacts.service + Add carddav scope to google-contacts.service (Yakkety) |
summary: |
- Add carddav scope to google-contacts.service (Yakkety) + Add carddav scope to google-contacts.service (Zesty) |
tags: |
added: zesty removed: yakkety |
Changed in evolution-data-server (Ubuntu): | |
status: | Fix Committed → Fix Released |
status: | Fix Released → Fix Committed |
summary: |
- Add carddav scope to google-contacts.service (Zesty) + [SRU] Add carddav scope to google-contacts.service |
tags: |
added: verification-needed removed: verification-failed |
Just providing the patch file for now.