<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 14, 2015 at 4:57 PM, Andy McKay <span dir="ltr"><<a href="mailto:amckay@mozilla.com" target="_blank">amckay@mozilla.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word"><div><br>We'll probably want to provide some sort of "token narrowing" API to<br>enable this in a more secure fashion.<br><br>If for example, Mozilla Concrete has a token with scope<br>"profile+payments+SuperSecretOtherThing", then it doesn't want to pass<br>that token directly to other services.  Instead, it could call some API<br>on the oauth server to generate a fresh subsidiary token with only<br>"payments" scope, and pass that token to the payments service.”</div></div></blockquote><div><br></div><div>We're working on "refresh" tokens for the oauth-server, which can request time-bound, scope-limited access tokens:<br><a href="https://github.com/mozilla/fxa-oauth-server/issues/209#issuecomment-78161848">https://github.com/mozilla/fxa-oauth-server/issues/209#issuecomment-78161848</a><br><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="word-wrap:break-word"><div><br></div><div>Any comments?</div></div><br></blockquote></div></div></div>