Bug 1354589 (bmo-oauth)

Implement OAuth2 on BMO

RESOLVED FIXED

Status

()

enhancement
P1
normal
RESOLVED FIXED
2 years ago
8 months ago

People

(Reporter: dylan, Assigned: dkl)

Tracking

(Blocks 1 bug, {bmo-goal})

Production
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(3 attachments, 1 obsolete attachment)

45 bytes, text/x-github-pull-request
Details | Review
45 bytes, text/x-github-pull-request
Details | Review
45 bytes, text/x-github-pull-request
Details | Review
Keywords: bmo-big
What's the driver for OAuth2? Compatibility? Requirements from another group?
Flags: needinfo?(mcote)
As discussed, this will mainly be for eventual Auth0 support.  Having a standard auth solution (as opposed to our custom API keys/auth delegation) would be nice too but not a priority.
Flags: needinfo?(mcote)
Backlogging this for now.

Getting a sizing on it and a date for when we'd need to support Auth0 would be useful.
Priority: -- → P3
Keywords: bmo-bigbmo-goal
Priority: P3 → P1
Depends on: bmo-mojo
Assignee: nobody → dkl
Status: NEW → ASSIGNED
Posted file GitHub Pull Request (obsolete) —
Posted file Schema Changes
Attachment #9025159 - Attachment description: GitHub Pull Request → Schema Changes
Posted file Client Admin
Attachment #9021191 - Attachment is obsolete: true
Posted file OAuth Plugin
Status: ASSIGNED → RESOLVED
Closed: 8 months ago
Resolution: --- → FIXED
Alias: bmo-oauth
You need to log in before you can comment on or make changes to this bug.