2010-09-06 17:34:42 |
Stuart Metcalfe |
bug |
|
|
added bug |
2010-09-06 17:35:13 |
Stuart Metcalfe |
bug task added |
|
launchpad-foundations |
|
2010-10-05 19:33:00 |
Gary Poster |
launchpad-foundations: status |
New |
Triaged |
|
2010-10-05 19:33:04 |
Gary Poster |
launchpad-foundations: importance |
Undecided |
Medium |
|
2010-10-16 16:20:52 |
Stuart Metcalfe |
canonical-identity-provider: importance |
Undecided |
Wishlist |
|
2010-10-16 16:21:03 |
Stuart Metcalfe |
canonical-identity-provider: status |
New |
Incomplete |
|
2010-10-16 16:23:31 |
Stuart Metcalfe |
summary |
Split remaining DB dependencies from LP |
[meta] Split remaining DB dependencies from LP |
|
2010-10-16 16:24:15 |
Stuart Metcalfe |
tags |
|
proj-splitit-final |
|
2010-10-16 16:25:21 |
Stuart Metcalfe |
description |
As part of https://dev.launchpad.net/LEP/OpenIdRoadmap
We currently replicate several tables from LP to support our teams implementation. We should be able to use the LP API for this. A few considerations:
* Some sites depend on the high availability of teams information and would be intolerant of LP downtime.
* LP doesn't expose an immutable user identifier so would things get a bit sticky if the user changed their email *and* username?
* Using the LP API could incur longer load times on SSO.
* We'd need a user-friendly and unobtrusive method of attaching your LP account to your SSO account. |
As part of https://dev.launchpad.net/LEP/OpenIdRoadmap
We currently replicate several tables from LP to support our teams implementation. We should be able to use the LP API for this. A few considerations:
* Some sites depend on the high availability of teams information and would be intolerant of LP downtime.
* LP doesn't expose an immutable user identifier so would things get a bit sticky if the user changed their email *and* username?
* Using the LP API could incur longer load times on SSO.
* We'd need a user-friendly and unobtrusive method of attaching your LP account to your SSO account.
Tag child bugs: proj-splitit-final
|
|
2010-10-20 09:24:28 |
Stuart Metcalfe |
bug task added |
|
canonical-isd |
|
2010-10-20 09:24:50 |
Stuart Metcalfe |
canonical-isd: status |
New |
Confirmed |
|
2010-10-20 09:24:58 |
Stuart Metcalfe |
canonical-isd: importance |
Undecided |
Medium |
|
2011-10-02 14:49:43 |
Curtis Hovey |
launchpad: importance |
Medium |
Low |
|
2011-10-02 21:30:10 |
Robert Collins |
launchpad: importance |
Low |
High |
|
2012-01-16 20:30:59 |
Robert Collins |
description |
As part of https://dev.launchpad.net/LEP/OpenIdRoadmap
We currently replicate several tables from LP to support our teams implementation. We should be able to use the LP API for this. A few considerations:
* Some sites depend on the high availability of teams information and would be intolerant of LP downtime.
* LP doesn't expose an immutable user identifier so would things get a bit sticky if the user changed their email *and* username?
* Using the LP API could incur longer load times on SSO.
* We'd need a user-friendly and unobtrusive method of attaching your LP account to your SSO account.
Tag child bugs: proj-splitit-final
|
As part of https://dev.launchpad.net/LEP/OpenIdRoadmap
We currently replicate several tables from LP to support our teams implementation. We should be able to use the LP API for this. A few considerations:
* Some sites depend on the high availability of teams information and would be intolerant of LP downtime.
* LP doesn't expose an immutable user identifier so would things get a bit sticky if the user changed their email *and* username?
* Using the LP API could incur longer load times on SSO.
* We'd need a user-friendly and unobtrusive method of attaching your LP account to your SSO account.
Tag child bugs: proj-splitit-final
See also
========
Bug 629169 |
|
2013-05-20 19:18:49 |
dobey |
canonical-identity-provider: status |
Incomplete |
Expired |
|