<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Apr 9, 2014, at 11:28 AM, Sean McArthur <<a href="mailto:smcarthur@mozilla.com">smcarthur@mozilla.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Apr 8, 2014 at 12:35 PM, Chris Karlof <span dir="ltr"><<a href="mailto:ckarlof@mozilla.com" target="_blank">ckarlof@mozilla.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div class=""><blockquote type="cite"><div dir="ltr">
- <b>[needs UX ]</b> for sign-up flow, permissions, forgot password (perhaps that order?)<br></div></blockquote><div><span style="white-space:pre-wrap"> </span></div></div><div>I don't think we need a permission screen for the early May deadline. Forgot password should be prioritized above that. </div>
<div class=""><br></div></div></blockquote><div><br></div><div>Yea, that sounds right. <b>John/Ryan</b>, whatcha think?<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div class=""><blockquote type="cite"><div dir="ltr"><div> - needs l10n for scopes, but only when we have more scopes, and RPs that aren't whitelisted (whitelisted apps/scopes are automatically approved)<br>
</div><br></div></blockquote><div><br></div></div><div>We can start this effort, but it shouldn't block, since we won't have a permission screen for initial reliers.</div><div class="">
<div><br></div></div></div></blockquote><div><br></div><div>Absolutely. This isn't needed until there are reliers we don't control (and aren't whitelisted).<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word"><div class=""><br></div><div>One thing missing from this is "relier libraries", e.g., common FxA visual elements (Sign in/Sign up/Logout buttons, signed in state), JS libs, etc.</div>
<div><br></div></div></blockquote><div><br></div><div>I'm working on nodejs library for request signing, which will be used by oauth-server and profile-server initially, and could be used by other reliers who use nodejs. Which else should we provide? Python, Ruby, Java?<br>
<br></div></div></div></div></blockquote><div><br></div><div>Can you provide more context on this request signing library? Is this for verifying signatures in the next-gen oauth-ish stuff you're working on with warner?</div><div><br></div><div>-chris</div><div><br></div><div><br></div><div><br></div></div><br></body></html>