Support BrowserID: Difference between revisions
(Created page with "==A brief description of what is proposed== Add support for using Raven to authenticate with Mozilla's [https://developer.mozilla.org/en/BrowserID BrowserID]. ==An explanation ...") |
|||
| Line 13: | Line 13: | ||
Support for this would actually be fairly simple. Mozilla provide | Support for this would actually be fairly simple. Mozilla provide | ||
* [http://identity.mozilla.com/post/17207734786/id-provider-support-now-live-on-browserid a basic intro] | |||
* [https://github.com/mozilla/browserid/blob/dev/docs/PRIMARY_PROTOCOL.md Documentation] | |||
* [https://github.com/lloyd/eyedee.me A fully working example] (written in node.js) | |||
Support really just involves providing a small number of web pages: | Support really just involves providing a small number of web pages: | ||
Declaration of support at https://cam.ac.uk/.well-known/browserid should be the JSON file: | Declaration of support at https://cam.ac.uk/.well-known/browserid should be the JSON file: | ||
{ | |||
{ | |||
} | "authority": "raven.cam.ac.uk" | ||
} | |||
The rest can then be implimented on the raven.cam.ac.uk domain (or another domain if preferable) and just consists of the declaration of support (provides public key and location of the other two pages), the authentication page (Sign the user in pretty much as per standard raven page except with a pre-determined e-mail and using AJAX) , and the provisioning page (check the user is authenticated and sign a certificate). | The rest can then be implimented on the raven.cam.ac.uk domain (or another domain if preferable) and just consists of the declaration of support (provides public key and location of the other two pages), the authentication page (Sign the user in pretty much as per standard raven page except with a pre-determined e-mail and using AJAX) , and the provisioning page (check the user is authenticated and sign a certificate). | ||
Latest revision as of 02:31, 13 April 2012
A brief description of what is proposed
Add support for using Raven to authenticate with Mozilla's BrowserID.
An explanation of how it would be useful
The key to achieving higher take-up of raven is to make implementation easier and slicker. Support for BrowserID would allow Raven to be used by users of systems which haven't specifically been set up for Raven, and would make it far easier to add support for raven to new websites. For instructions on using browser id see https://developer.mozilla.org/en/BrowserID/Quick_Setup
Sibboleth (have I spelt that right?) isn't getting much use because it's unnecessarily complex to use, and because authentication and profile information really should be two separate steps. BrowserID would be a much simpler and more popular alternative and would be especially useful for things like society websites where not all users are university members.
One or more suggestions of how it could be implemented
Support for this would actually be fairly simple. Mozilla provide
- a basic intro
- Documentation
- A fully working example (written in node.js)
Support really just involves providing a small number of web pages:
Declaration of support at https://cam.ac.uk/.well-known/browserid should be the JSON file:
{
"authority": "raven.cam.ac.uk"
}
The rest can then be implimented on the raven.cam.ac.uk domain (or another domain if preferable) and just consists of the declaration of support (provides public key and location of the other two pages), the authentication page (Sign the user in pretty much as per standard raven page except with a pre-determined e-mail and using AJAX) , and the provisioning page (check the user is authenticated and sign a certificate).
