Canonical SSO provider

Enhance diagnostic output of the account-merging script

Bug #721318 reported by David Owen on 2011-02-18

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Canonical SSO provider	Fix Released	Low	David Owen	Canonical SSO provider 11.03.15

Bug Description

When safety checks fail, additional information could be printed to the user to explain the failure. Here's a good description:

08:18 < stuartm> it's not an openid association as in something which can be
                 recreated. we're saying that he has used the account to log in
                 to a remote site and by effectively deleting the account on
                 sso he will need to create a new account on the remote site
                 and will lose all historical data

Additionally, the script should print a list of sites that would be affected. The query could be as simple as:

account.last_authenticated_sites()

Tags:

Related branches

lp://staging/~canonical-isd-hackers/canonical-identity-provider/721318-enhance-merge

Merged into lp://staging/~canonical-isd-hackers/canonical-identity-provider/stable at revision 95

Michael Nelson (community): Approve on 2011-02-24

Canonical ISD bug wrangler (isd-bug-wrangler) on 2011-02-18

Changed in canonical-identity-provider:
assignee:	nobody → David Owen (dsowen)
importance:	Undecided → Low
status:	New → In Progress
tags:	added: kb-task

Canonical ISD bug wrangler (isd-bug-wrangler) on 2011-02-25

Changed in canonical-identity-provider:
status:	In Progress → Fix Committed

Revision history for this message

Ricardo Kirkner (ricardokirkner) wrote on 2011-03-14:

Notes for QA:

This script is intended to be run against the production db. However to test this, the merge-accounts script can be run and see that it warns about the merge source account and lists all sites the account was used.

Revision history for this message

Ricardo Kirkner (ricardokirkner) wrote on 2011-03-14:

There is not much point in testing this before staging, as no service uses the vps as an sso provider, so no information will be shown by the command that would be shown in staging/prod.

To test this on staging:

1. create two accounts
2. use one of those accounts to login to staging.pay
3. request merge of the two accounts (using the merge-accounts) script
4. verify the warning message and that it lists staging.pay
5. go ahead and merge the accounts
6. verify that there is only one account left, and that it still works

Ricardo Kirkner (ricardokirkner) on 2011-03-15