Confirmed users
1,052
edits
Identity/BrowserID/IntranetPhonebook: Difference between revisions
Jump to navigation
Jump to search
Identity/BrowserID/IntranetPhonebook (view source)
Revision as of 23:39, 19 September 2011
, 19 September 2011→Scope
No edit summary |
(→Scope) |
||
| Line 2: | Line 2: | ||
As a feature enhancement, we want to implement BrowserID to login to the MoCo phonebook. If we can avoid "fixing" our internal infrastructure before shipping this, that would be great. Of course bringing up to a safe standard so that we can deploy well tested changes is totally reasonable. | As a feature enhancement, we want to implement BrowserID to login to the MoCo phonebook. If we can avoid "fixing" our internal infrastructure before shipping this, that would be great. Of course bringing up to a safe standard so that we can deploy well tested changes is totally reasonable. | ||
= Scope = | |||
1) Add a new auth mechanism to the slapd server | 1) Add a new auth mechanism to the slapd server | ||
| Line 17: | Line 17: | ||
Instead of slapd doing auth with username/email and password... it will get a BrowserID assertion and audience from the PHP code. It will then delegate to the plugin which will verify the assertion with browserid.org. If everything goes well, slapd will see the user as authenticated. If there are any issues or the user doesn't exist in ldap, the user will see an auth error. | Instead of slapd doing auth with username/email and password... it will get a BrowserID assertion and audience from the PHP code. It will then delegate to the plugin which will verify the assertion with browserid.org. If everything goes well, slapd will see the user as authenticated. If there are any issues or the user doesn't exist in ldap, the user will see an auth error. | ||
== Changes == | |||
We will add the [https://github.com/ozten/sasl-browserid sasl-browserid plugin] to our LDAP server. | We will add the [https://github.com/ozten/sasl-browserid sasl-browserid plugin] to our LDAP server. | ||