https://api.mozillapulse.org/ social login displaying a 403 error

[danielfmiranda]

If you visit https://api.mozillapulse.org/ and click "go to the admin website" it should display 3 options to log in being:

• google
• github
• admin site

However, when you click this button it instead displays a 403.

[Pomax]

Does the heroku log show anything we can use to figure out why it's claiming 403?

[Pomax]

It looks like this happens when recaptcha is turned on, where it locks down the "from the admin site itself" login path, not just the one from pulse.

The immediate way around this is to always log in through the front end, rather than directly through the backend (as that will include the recaptcha data). The "proper" solution is to either add the recaptcha code to the admin login template (see templates/users/index.html) or, once account moderation has landed, we can probably remove recaptcha on pulse again because new signups won't be able to do anything until their account is marked as active by a moderator.

[danielfmiranda]

This ticket should wait until the work in #798 is complete