Comment 7 for bug 901336

@ricardo: that would be ideal if sca could subscribe to such events.

In the mean-time, sca already (attempts to [1]) update to the current LP username the next time the user initiates a purchase (which will update the exported deblines for all purchases). We could use this same call (check_or_create_lp_user) to verify / update the username when USC requests the list of subscriptions for a user (ie. so the exported deb-lines include the correct username). This would mean that users could simply "Reinstall previous purchases" to sort the issue out? [2]

[1] We currently have a related issue that the new username may already be present in sca and we blindly try to save a second user record with the same username, rather than (possibly) moving the subscription/openid over to the existing django user or vice-versa.

[2] Although I assume USC would need to handle remove the old entries if they are found while trying to add the new ones?