977748 - [traceback] unable to log in to staging/prod due to ImproperlyConfigured: Required setting BROWSERID_AUDIENCES not found!

Status: RESOLVED FIXED

(Socorro Graveyard :: Middleware, defect)

Description

[Stephen Donner [:stephend] Not actively reading bugmail]

I can't sign in on prod or staging, due to:

https://errormill.mozilla.org/webtools/socorro-prod/group/165968/

ImproperlyConfigured: Required setting BROWSERID_AUDIENCES not found!

Stacktrace (most recent call last):

  File "django/core/handlers/base.py", line 111, in get_response
    response = callback(request, *callback_args, **callback_kwargs)
  File "django/views/generic/base.py", line 48, in view
    return self.dispatch(request, *args, **kwargs)
  File "django_browserid/views.py", line 107, in dispatch
    return super(Verify, self).dispatch(request, *args, **kwargs)
  File "django/views/generic/base.py", line 69, in dispatch
    return handler(request, *args, **kwargs)
  File "django_browserid/views.py", line 93, in post
    self.user = auth.authenticate(request=self.request, assertion=assertion)
  File "django/contrib/auth/__init__.py", line 45, in authenticate
    user = backend.authenticate(**credentials)
  File "django_browserid/auth.py", line 115, in authenticate
    audience = get_audience(request)
  File "django_browserid/base.py", line 93, in get_audience
    raise ImproperlyConfigured('Required setting BROWSERID_AUDIENCES not found!')

We (sadly) dont' have a test for this (at least in Web QA), so I'll get an Issue filed in GitHub to get one ASAP.

http://screencast.com/t/facTuT55XulA

Comment 1

[Stephen Donner [:stephend] Not actively reading bugmail]

(In reply to Stephen Donner [:stephend] from comment #0)

> We (sadly) dont' have a test for this (at least in Web QA), so I'll get an
> Issue filed in GitHub to get one ASAP.

https://github.com/mozilla/Socorro-Tests/issues/252 covers this needed automation test.

Comment 2

[Peter Bengtsson [:peterbe]]

977751 is resolved. I think you can resolve this bug now. Stage is currently down but prod definitely works. (...to sign in).

Comment 3

[Peter Bengtsson [:peterbe]]

977751 is resolved. I think you can resolve this bug now. Stage is currently down but prod definitely works. (...to sign in).

Comment 4

[Matt Brandt [:mbrandt]]

> We (sadly) dont' have a test for this (at least in Web QA), so I'll get an
> Issue filed in GitHub to get one ASAP.

:stephend thank you for filing git issue. Note previously this was an area that the team decided not to have QA responsible for automation on. Sounds like we need it.

Comment 5

[Lonnen :lonnen]

can now sign in to stage and prod. no longer seeing this error.