Closed Bug 1846663 Opened 2 years ago Closed 1 year ago

SUMO article: Enabling 3rd party authentication for FxA

Categories

(support.mozilla.org :: Knowledge Base Content, task)

Product:
support.mozilla.org
Component:
Knowledge Base Content
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: vzare, Assigned: dgalindo)

Details

Product

Firefox account

Select the type of request

New feature or functionality

##What is the anticipated release date? [REQUIRED]
Go Live with FxA train 266 on September 6.

##What is the proposed deadline for the content to be published? [REQUIRED]
September 20.

Please include any related JIRA/Github/Bugzilla tickets, documentation, demos or practical use cases. [REQUIRED]

We need a new article to introduce Google/Apple Authentication as an alternative method of authentication for customers registering or logging into FxA. Customers who register for a Firefox account by authenticating through Google/Apple do not need to create a password. This feature will not appear on the Sync flow since Sync customers will always require to create a password.

https://docs.google.com/document/d/1qtpGJrtiGgPYVy9Ep7EeLXHAe_48eG2_V7V9a4ypdcg/edit

Scenarios to cover (meeting has been scheduled to review this)

  • How to register or login with Google/Apple ID
  • Why you can't register for Sync using Google/Apple ID
  • How unlinking your Google/Apple account from your FxA does NOT log you out of your Google/Apple account in your browser
  • What to do if you no longer want to authenticate using Google/Apple.
    Handling data:
  • What data do we receive from Google/Apple? Email address (we use), profile picture (we don't use)
  • Do we provide any data back to Google/Apple? No

Does the content need to be localized in any languages outside of our priority locales (yes or no)?

Same treatment as other FxA articles

Does the content require legal review (yes or no)?

I don't think so

Is the content embargoed (yes or no)?

No

Assignee: nobody → aparise

Hello! Update on timing: We're now aiming to launch this feature on 20 Sept (instead of 6 Sept).

Is this article on track to be ready by 6 Sept?

Thanks!

Flags: needinfo?(aparise)

Hi Jess! I will be working on this update this week to get content ready. I'll reach out with any questions!

Flags: needinfo?(aparise)
Status: NEW → ASSIGNED

Hey Abby! How's this going? We're currently on track for a launch on 20 Sept (next week) and want to make sure we're all good to go with this SUMO article.

Thanks!

Flags: needinfo?(aparise)

The articles are ready for review & verification!
https://docs.google.com/document/d/1A00uy0sZIqUjKeG7iL7uBHlCA1oFMNd1Aa1o0JkGeK4/edit?usp=sharing

Flags: needinfo?(aparise)
Assignee: aparise → dgalindo

Hi Dayani, just checking in—could you confirm if Abby’s requested changes have been made and if this ticket is ready to be closed? Appreciate it!

Flags: needinfo?(dgalindo)
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED

I don't have access to the Google Doc that Abby linked in comment 5 but I see that she created/approved these articles based on this bug:

Michele Rodaro (michro) submitted another revision to correct broken links under "Related articles" and I made a few more edits. Lucas, can you review these revisions? See https://support.mozilla.org/en-US/kb/sign-in-accounts-using-3rd-party-auth/history

Flags: needinfo?(lsiebert)
Flags: needinfo?(lsiebert)
You need to log in before you can comment on or make changes to this bug.