Closed Bug 1713543 Opened 4 years ago Closed 4 years ago

Use Thunderbird OAuth credentials for new Google calendars

Categories

(Calendar :: Provider: CalDAV, task)

Tracking

(thunderbird_esr78 unaffected)

RESOLVED FIXED
91 Branch
Tracking Status
thunderbird_esr78 --- unaffected

People

(Reporter: darktrojan, Assigned: darktrojan)

References

Details

Attachments

(1 file)

The OAuth credentials we use for Google Calendar are still those of Lightning. In this bug I'm going to modify the code so that if a new calendar is created (or if somehow an existing one loses its tokens) the Thunderbird credentials are used. This shouldn't affect existing calendars.

Where there's no saved password, use Thunderbird's credentials instead of Lightning's. Store saved tokens with a different string so that we can automatically which set to use:

  • Tokens using Thunderbird's credentials will appear in the password manager as 'oauth://accounts.google.com (https://www.googleapis.com/auth/calendar)' which matches other OAuth uses.
  • Tokens using Lightning's credentials will continue to appear as 'oauth:{session id} (Google CalDAV v2)'.

Pushed by geoff@darktrojan.net:
https://hg.mozilla.org/comm-central/rev/de4e453066c0
Use Thunderbird OAuth credentials for new Google calendars. r=mkmelin

Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → 91 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: