Allow trusted internal apps to read profile information without user interaction about fxa HOT 9 CLOSED

The concrete implementation here will likely look a lot like "OAuth2 Service Tokens" and feel very similar to the way it works in Google's infrastructure:

https://developers.google.com/identity/protocols/OAuth2ServiceAccount

@edmoz @billmaggs we'll need to coordinate with the payments team to determine the right timeline for this, but I think we need to ship it this quarter.

@seanmonstar since you're driving this effort, I've assigned the feature card to you.

from fxa.

Will check with Andy McKay on timing for payments. Their dates have been
slipping.

On Wed, Aug 19, 2015 at 9:11 PM, Ryan Kelly [email protected]
wrote:

The concrete implementation here will likely look a lot like "OAuth2
Service Tokens" and feel very similar to the way it works in Google's
infrastructure:

https://developers.google.com/identity/protocols/OAuth2ServiceAccount

@edmoz https://github.com/edmoz @billmaggs
https://github.com/billmaggs we'll need to coordinate with the payments
team to determine the right timeline for this, but I think we need to ship
it this quarter.

@seanmonstar https://github.com/seanmonstar since you're driving this
effort, I've assigned the feature card to you.

—
Reply to this email directly or view it on GitHub
#53 (comment).

from fxa.

Feedback from Andy is that this is no longer an immediate priority for them, and that Q4 or even Q1 would be fine for their purposes.

from fxa.

Does that affect us, or still planning this for Q3?

from fxa.

I assume the basket team still needs this this quarter; the payments team does not. Ryan, is that the case?

from fxa.

Yes, let's still aim to get it done this quarter, it will be useful for a variety of more-internal stuff as well as for payments, kinto etc as external consumers.

from fxa.

I've updated this issue to include a list of implementation details needed to fully close this.

from fxa.

Exporting these FEATURE cards from Aha has not turned out to be useful in practise, I'm closing them in favour of more direct use of Aha.

This feature lives at: https://mozilla.aha.io/features/FXA-31

from fxa.

I also created a milestone and migrated the existing issues into it, so we don't lose any context from this bug:

https://waffle.io/mozilla/fxa?milestone=FxA-31:%20service%20tokens

from fxa.