Closed
Bug 843795
Opened 11 years ago
Closed 11 years ago
Login error: Persona assertion expired, periodically on B2G
Categories
(Marketplace Graveyard :: Consumer Pages, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: kumar, Unassigned)
References
Details
Every couple days (sometimes weeks) I can't log in to Marketplace on B2G because of an "assertion expired" error. When I rebuild my profile the error goes away. I've seen it on many different versions: localhost, dev, stage, etc. Here is the latest failure on stage so you can unpack the assertion and check it out. Maybe something is cached client side that shouldn't be? Feb 21 13:05:45 web6.stage.addons.phx1.mozilla.com: [][] django_browserid.base:INFO Verification URL: https://native-persona.org/verify :/data/www/addons.allizom.org/venv/src/django-browserid/django_browserid/base.py:109 Feb 21 13:05:45 web6.stage.addons.phx1.mozilla.com: [][] django_browserid.base:ERROR BrowserID verification failure. Response: {u'status': u'failure', u'reason': u'assertion has expired'} Audience: https://marketplace.allizom.org :/data/www/addons.allizom.org/venv/src/django-browserid/django_browserid/base.py:121 Feb 21 13:05:45 web6.stage.addons.phx1.mozilla.com: [][] django_browserid.base:ERROR BID assert: eyJhbGciOiJSUzI1NiJ9.eyJwdWJsaWMta2V5Ijp7ImFsZ29yaXRobSI6IkRTIiwieSI6IjcyYjEyMGY3ZDljMzIxMzFmOWUzY2I5NDU3ODc4MzI4NGM3YzhmYmJlMjkxYzVjMzM2OGRkNjgyMzA2MjM0MWRlYjAxYzEyMzIxNjM0OWM4ODVhNDM0NGY4Mzg1ZGViOTQzMWY4ZTg1NzA2MmI3Y2UxODEyNjQyZDJjODFiYTZkNDQxNzE1NjU4ODQyNjUyYjllZGM5NTY0NDYyNjdiN2ExN2JiNzZjNWRlNGQ3NTU1NzZlMTlhMmUyMDZlNTczZDMxNzBjNjg2NjQyNzAxMzY2NjQ2NDRmODc4OTRiNGY2MWFlNmM4MDY5MTM4MWE4NjU1ZWIzOTFlOTkyNjhkNjkiLCJwIjoiZmY2MDA0ODNkYjZhYmZjNWI0NWVhYjc4NTk0YjM1MzNkNTUwZDlmMWJmMmE5OTJhN2E4ZGFhNmRjMzRmODA0NWFkNGU2ZTBjNDI5ZDMzNGVlZWFhZWZkN2UyM2Q0ODEwYmUwMGU0Y2MxNDkyY2JhMzI1YmE4MWZmMmQ1YTViMzA1YThkMTdlYjNiZjRhMDZhMzQ5ZDM5MmUwMGQzMjk3NDRhNTE3OTM4MDM0NGU4MmExOGM0NzkzMzQzOGY4OTFlMjJhZWVmODEyZDY5YzhmNzVlMzI2Y2I3MGVhMDAwYzNmNzc2ZGZkYmQ2MDQ2MzhjMmVmNzE3ZmMyNmQwMmUxNyIsInEiOiJlMjFlMDRmOTExZDFlZDc5OTEwMDhlY2FhYjNiZjc3NTk4NDMwOWMzIiwiZyI6ImM1MmE0YTBmZjNiN2U2MWZkZjE4NjdjZTg0MTM4MzY5YTYxNTRmNGFmYTkyOTY2ZTNjODI3ZTI1Y2ZhNmNmNTA4YjkwZTVkZTQxOWUxMzM3ZTA3YTJlOWUyYTNjZDVkZWE3MDRkMTc1ZjhlYmY2YWYzOTdkNjllMTEwYjk2YWZiMTdjN2EwMzI1OTMyOWU0ODI5YjBkMDNiYmM3ODk2YjE1YjRhZGU1M2UxMzA4NThjYzM0ZDk2MjY5YWE4OTA0MWY0MDkxMzZjNzI0MmEzODg5NWM5ZDViY2NhZDRmMzg5YWYxZDdhNGJkMTM5OGJkMDcyZGZmYTg5NjIzMzM5N2EifSwicHJpbmNpcGFsIjp7InVudmVyaWZpZWQtZW1haWwiOiJrdW1hci5tY21pbGxhbitxMkBnbWFpbC5jb20ifSwiaWF0IjoxMzYxNDcxMDk0NzA5LCJleHAiOjEzNjE0NzQ2OTQ3MDksImlzcyI6ImIyZzJwYWMucGVyc29uYXRlc3Qub3JnIn0.BLUi8HmIxX-zLlCuj6apipnBt8iI5FcZ8joqVa0Y9HrpGBmFZI_318AdHZuHm7Jw0tcldJ268KNmWflrt3wF2eiNcAKlYFh1-HZ9-B88sndYgTYNx03g0AC62Az-RGwuPiVCOzZp_QdiqQMZGvKsQbApYNZKH3mVeyT5oonb1OC8eirZ3wg25oZhqpweOkQItArXaw4YwYQBUiJ9Twv9_c8fmVtnI_Q3sAXOTANitWpQyoPqhGHcNHX2Us0Lqco7oXQlf0W4H51Uqq2JEGsyH5Y0wV8yJzJe8_KziMHoOcevhjVVowAYKoMoVlPgMKCD-3FfQvAOAowyGAUNNGOB4w~eyJhbGciOiJEUzEyOCJ9.eyJleHAiOjEzNjE0ODA4NjM3MjcsImF1ZCI6Imh0dHBzOi8vbWFya2V0cGxhY2UuYWxsaXpvbS5vcmcifQ.ZLQH_YPbB6AKQRM5Tffc-MfQ0AkMrisQxrhiCHkGgySSSjd909bTTQ
Reporter | ||
Updated•11 years ago
|
Blocks: marketplace-payments
Comment 1•11 years ago
|
||
Created browserid issue https://github.com/mozilla/browserid/issues/3033
Reporter | ||
Comment 2•11 years ago
|
||
A lot of folks are running into this. If you haven't ever rebuilt a profile before then you can do two things: 1) re-download the latest unagi.zip and simply re-flash your phone 2) build a profile from the gaia source and push it to your phone per https://github.com/mozilla/webpay#build-a-custom-b2g-profile (this does not required building firefox os itself)
Comment 3•11 years ago
|
||
using the in-os reset function works too, fwiw.
Reporter | ||
Comment 5•11 years ago
|
||
Great, thanks eviljeff. This is easier: Go to Settings > Device information > More Information > Reset Phone
Reporter | ||
Updated•11 years ago
|
Priority: -- → P1
Reporter | ||
Comment 6•11 years ago
|
||
It looks like bug 839500 is going to fix this
Reporter | ||
Comment 7•11 years ago
|
||
As per the bug, the change has landed on b2g18/v1-train. If anyone sees this after updating, can you re-open?
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•