Come on, it only makes sense, if we're going to have SSO at all.
Description
Supposedly the contact for Ubuntu One (login.ubuntu.com) is isd-support@canonical.com. Just dropped them an email.
Here's the response:
Ubuntu SSO is an openid identity provider (see for example askubuntu.com where you can use Launchpad as your identity). If Phabricator supports openid, you could use that to integrate easily.
It unfortunately doesn't support LDAP, and only supports OAuth 1.
Feel free to bzr branch lp:canonical-identity-provider and check out docs/resources/token.txt for info on how to get oauth tokens. This is, for example, the authentication mechanism old versions of Ubuntu Software Center used. Be warned that oauth support might go away in the future though.
You can also file a bug at https://bugs.launchpad.net/canonical-identity-provider/ to get it to the wider attention of SSO developers, because this address is mainly for login issues and as such, the visibility and help I can provide are limited.
I'll look more into this.
Unfortunately it looks like the request for OpenID auth was denied but I'll see if I can find some more information as that's a little old.
Dropped a message on the Phabricator community support forum (which, in an example of poor dogfooding, is not Phabricator but Discourse). Hopefully someone will have some sort of solution.
It is open source after all... You might be able to write a plugin for our instance and make it a Git submodule that you put on GitHub somewhere...
Would you be open to writing that code?
OAuth1 is the way to go: it's supported by Phabricator (see Twitter, BitBucket, JIRA providers) and Ubuntu SSO (though they don't guarantee they won't drop it).
Made a Google Code-In task to try to get this solved. It's a doozy so I'm not sure we're going to get it done. That said, here's the basics:
- generating Ubuntu SSO OAuth1 tokens
- generic Phabricator OAuth1 provider (go up one folder and you'll see all the providers including the aforementioned ones that already use OAuth1)
OAuth1 is the way to go: it's supported by Phabricator (see Twitter, BitBucket, JIRA providers) and Ubuntu SSO (though they don't guarantee they won't drop it).
Fine by me.
Made a Google Code-In task to try to get this solved. It's a doozy so I'm not sure we're going to get it done.
Bah, I've made complex packaging guide tasks, there's a few students who like this stuff enough that they'll fight through it (go them!). ๐
That said, here's the basics:
generating Ubuntu SSO OAuth1 tokens generic Phabricator OAuth1 provider (go up one folder and you'll see all the providers including the aforementioned ones that already use OAuth1)
Added this page to the GCI task, as a bonus thing. ๐