There is no timeline for FxA to support third party services (i.e., non-Mozilla services) at the present. Third-party services using Persona should continue to use Persona.
Otherwise, for experimenting with FxA, you can self-provision credentials at https://oauth-latest.dev.lcip.org/console. Login requires a FxA with a mozilla.com email address. It’s a bit “basic” at this point, in the sense that anyone who can log in can change any OAuth configuration in the dev environment. Feel free to try it out for your test sites, and let us know if you have any questions. -chris On Dec 8, 2014, at 10:02 AM, Michael Kelly <[email protected]> wrote: > Yo! In preparation for people starting to ask about porting a site using > Persona via django-browserid to using FxA, I'm playing around with getting > FxA login working on a few local copies of my sites using django-allauth. > > I don't plan on actually updating any of these sites yet, but I still need > credentials to test the flow out (I think; I know little-to-nothing about > OAuth. Maybe I don't need them?). > > May I please get testing credentials? One issue is that I won't have an HTTPS > endpoint to redirect back to since this is just local testing, so it'll be > HTTP; is that a big problem? > > Name: Django BrowserID Porting Test > Redirect URI: http://localhost:8000/fxa/redirect > > Thanks! > - Mike Kelly > _______________________________________________ > Dev-fxacct mailing list > [email protected] > https://mail.mozilla.org/listinfo/dev-fxacct _______________________________________________ Dev-fxacct mailing list [email protected] https://mail.mozilla.org/listinfo/dev-fxacct
