This will contain dependency bugs for getting oauth tokens on the production f1 server
bug 648892 has the service name, which is Share. For OAuth app setup, I am assuming it would be Firefox Share.
Depends on: 648892
bug 648894 is for the share logo/icon
note, other than facebook, the oauth app configuration is tied to a single account, you will probably want a services account for that.
FYI, we'll be getting 2 sets of oauth tokens (one for stage, one for prod). as far as service usernames/emails, I'll plan on something like: infra-services+foo-prod@.mc firstname.lastname@example.org
I think I'd prefer if it's not just infra-services that gets mail if something goes haywire. Someone (clarkbw?)was filing an itreq for an appropriate zimbra alias that'd include infra-services, myself, Bryan Clark, and probably others.
So what should we call this list? services-oauth@? I didn't consider the case where a third-party provider emails the oauth token contact to complain about abuse or something.
Bug 651658 has the request for the email alias.
We've created email@example.com via Bug 651658. If you have any questions or concerns for this bug feel free to contact desktop support.
services-oauth@ list now includes infra-services, clarkbw, and mconnor. created accounts under that email for twitter & google, acquired oauth keys. facebook doesn't support group accounts, and I have some pending questions on what to put in the app create form. But once I do create the app there, I'll grant the members of the mailing list admin privs in facebook.
Assignee: nobody → petef
Status: NEW → ASSIGNED
(In reply to comment #9) > facebook doesn't support group accounts, and I have some pending questions on > what to put in the app create form. But once I do create the app there, I'll > grant the members of the mailing list admin privs in facebook. product marketing, bug 648892, is going to help with the copy required for the app page.
share server component deprecated, closing
Status: ASSIGNED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.