Closed Bug 879091 Opened 11 years ago Closed 11 years ago

Bango should prompt fresh authentication after every log in

Categories

(Marketplace Graveyard :: Payments/Refunds, defect, P4)

defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 872751

People

(Reporter: krupa.mozbugs, Unassigned)

References

Details

steps to reproduce:
1. Using a movistar SIM, make a purchase on wifi confirming your mobile number
2. After successful purchase, replace the movistar SIM with a T-mobile SIM
3. Log out (This will be done automatically done when bug 872751 is implemented)
4. Log in using the same account

expected behavior:
Bug 872751 takes care of users switching SIMs and making purchases. After a log out, Bango should force authentication even for existing accounts

observed behavior:
Even after log in, Bango reuses the mobileID from before. My purchases are still getting billed to my Movistar info even after i switched SIMs and relogged in.
Summary: Bango shouldn prompt fresh authentication after every log in → Bango should prompt fresh authentication after every log in
This is not a Bango bug. We don't currently have any reliable and non-hacky way to trigger a Bango logout from the Marketplace logout. The Marketplace app is completely separate and isolated from the Webpay process which runs in the Trusted UI.

I'm making this a P4 because I don't see how this causes a problem. Is there a reason why it's something more severe then a P4?

bug 858273 is also a related issue but it's the reverse: webpay logout is not connected to a marketplace logout
Assignee: keir → nobody
Priority: -- → P4
btw, passing a user ID to Bango for Venezuela (bug 877923) will make this same behavior happen all the time. Once you log in and save your payment info, every other time you log in (on desktop, mobile, etc), you'll see your saved info. I think this will be a nice convenience for a user, not a bug.
Flags: affects-tricycle+
Flags: affects-seville+
Flags: affects-seahorse+
Flags: affects-moss+
Flags: affects-durango+
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.