On Tue, Apr 14, 2015 at 4:57 PM, Andy McKay <[email protected]> wrote:
> > We'll probably want to provide some sort of "token narrowing" API to > enable this in a more secure fashion. > > If for example, Mozilla Concrete has a token with scope > "profile+payments+SuperSecretOtherThing", then it doesn't want to pass > that token directly to other services. Instead, it could call some API > on the oauth server to generate a fresh subsidiary token with only > "payments" scope, and pass that token to the payments service.” > We're working on "refresh" tokens for the oauth-server, which can request time-bound, scope-limited access tokens: https://github.com/mozilla/fxa-oauth-server/issues/209#issuecomment-78161848 > Any comments? > >
_______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
