Hi Mike, we have to manually provision credentials for prod, there is not automatic escalation path. I have opened [1] to provision credentials on our stage and prod servers.
Shane [1] - https://bugzilla.mozilla.org/show_bug.cgi?id=1566346 On Mon, Jul 15, 2019 at 10:25 PM Michael Comella <mcome...@mozilla.com> wrote: > Hi Shane, > > When do the credentials merged to the dev server move onto the production > Firefox Accounts server? > - Mike > > On Tue, Jul 2, 2019 at 4:43 PM Michael Comella <mcome...@mozilla.com> > wrote: > >> Hi Shane, >> >> On Tue, Jul 2, 2019 at 4:22 AM Shane Tomlinson <stomlin...@mozilla.com> >> wrote: >> >>> Hi Mike, >>> Those docs are a bit out of date now and need to be updated (on Q3's OKR >>> list), sorry for the confusion. It shouldn't be a problem to get you set up >>> with OAuth credentials. >>> >>> As mentioned in the docs development occurs against the >>> https://stable.dev.lcip.org FxA stack. stable is a prod-like stack that >>> is updated every Thursday. Note that it's user database is distinct to >>> https://accounts.firefox.com, so developers will need to create and >>> verify an account there to sign into the app. OAuth credentials for >>> https://accounts.firefox.com are reserved for your beta/production apps. >>> >>> I have created a PR to provision creds >>> <https://github.com/mozilla/fxa-dev/pull/468> on >>> https://stable.dev.lcip.org for you. If that looks good to you, we can >>> get that deployed soon. >>> >> >> Given my limited knowledge, this looks good to me. >> >> When would create beta/production credentials? >> >>> >>> Will Firefox for Fire TV access Sync data? I'm assuming so. >>> >> >> In the short term (Q3), we only intend to receive tabs. We have no >> current plans to use sync data otherwise. >> >>> >>> I know from speaking to Chenxia that there are a few wriggles that need >>> to be ironed out for Fx for Fire TV, especially around navigation and >>> input. Email verification is going to be interesting too, I wonder if users >>> will find it obvious how to verify their email. We have been talking about >>> making all users verify their email address by typing a TOTP-like code >>> <https://github.com/mozilla/fxa/issues/457> that is sent to their email >>> address, in this case, since Firefox for Fire TV is input constrained, it >>> might make sense to have continue with the existing behavior and have users >>> click a link instead. >>> >> >> Our intent is to land a proof-of-concept FxA sign in integration ASAP to >> be able to test all the flows on device and figure out the optimal user >> experience. Bram, our UX designer, may have already done some research with >> your team here but fwiw, I'm missing context on it. >> >> Thanks for the quick response – let me know if you have any questions or >> suggestions for me! I don't have much context on the FxA integration so I'm >> currently in the process of figuring it out in this issue >> <https://github.com/mozilla-mobile/firefox-tv/issues/2445>. >> - Mike >> >>> >>> Shane >>> >>> On Tue, Jul 2, 2019 at 2:17 AM Michael Comella <mcome...@mozilla.com> >>> wrote: >>> >>>> Hey dev-fxacct (CC firefox-tv list for context), >>>> >>>> The Firefox for Fire TV app is integrating FxA sign in and I'd like to >>>> get credentials to enable sign in. I don't fully understand the >>>> documentation >>>> <https://mozilla.github.io/application-services/docs/accounts/welcome.html#becoming-a-firefox-accounts-relier> >>>> – it suggests that our app is an "OAuth relier" (what does that mean?) and >>>> that we have a "service" (is the app considered a service?) – but from >>>> reading the docs and looking at samples >>>> <https://github.com/mozilla-mobile/android-components/tree/master/samples/firefox-accounts>, >>>> I think if we provide the following info, we can get credentials to allow >>>> users to log into FxA: >>>> >>>> name: "Firefox for Fire TV" >>>> redirect_uri: https://accounts.firefox.com/oauth/success/<clientId> >>>> >>>> fwiw, like the sample linked above, we'd intend to intercept the >>>> redirect URL, grab the returned credentials, and redirect the user to a >>>> native UI screen (as per our mocks) >>>> <https://whimsical.com/Mbrga1N3KwHiJpExhSR23m>. Additionally, since we >>>> can't create additional WebViews on Fire OS and we only support a single >>>> tab, we have to use the user's current browsing session so we'd consider >>>> removing the FxA sign in pages from the user's browsing history. >>>> >>>> Let me know if there are any issues. Thanks! >>>> - Mike >>>> _______________________________________________ >>>> Dev-fxacct mailing list >>>> Dev-fxacct@mozilla.org >>>> https://mail.mozilla.org/listinfo/dev-fxacct >>>> >>>
_______________________________________________ Dev-fxacct mailing list Dev-fxacct@mozilla.org https://mail.mozilla.org/listinfo/dev-fxacct
