search

mozilla / m-response

Crowdsourcing Mozilla responses to Google Play Store reviews
Mozilla Public License 2.0
12 stars 10 forks source link

Unable to log into front-end on staging #257

Closed natalieblackburn closed 5 years ago

natalieblackburn commented 5 years ago

You can't currently log in to the front-end view on staging as a normal user, only via the admin first. To be able to test the permissions, we need to be able to log in as end users to the front-end of the application on staging

Current behaviour: go to https://mozilla-respond-qa.herokuapp.com/ and select to log in, see a blank screen and this URL: https://mozilla-respond-qa.herokuapp.com/oidc/authenticate/None/?response_type=code&scope=openid+email&client_id=None&redirect_uri=https%3A%2F%2Fmozilla-respond-qa.herokuapp.com%2Foidc%2Fcallback%2F&state=sublPA7vU7C3Ywlk3i942BzVWbTo21g5&nonce=v9nZBlOXcJjJrxzbYYt4p3AkdsrAQNGI

natalieblackburn commented 5 years ago

Create a basic django login / reconfigure what's existing to find the quickest solution to being able to log in as a user to the front-end of the app without a staff account, to enable testing. Timebox to 1hr

tm-kn commented 5 years ago

This is on the dev server - https://mozilla-respond-qa.herokuapp.com/oidc/authenticate/

natalieblackburn commented 5 years ago

Tomasz is looking into this further, it seems to check the credentials OK and I can log in using correct details for a test user, but accessing /dashboard is showing a blank screen, so looks like there is a front-end bug stopping the usual page displaying

tm-kn commented 5 years ago

@natalieblackburn Try now. I think I've fixed the front-end issue.

natalieblackburn commented 5 years ago

Interestingly it works fine logging in on my own account (as an admin user), I can get in through this new link and see the dashboard. When I try logging in as tbx-test with correct credentials though, I still see a blank screen at /dashboard.

I also tried creating a new non-admin user to test with instead of that one, and got a 500 server error

tm-kn commented 5 years ago

I've tested it with a couple of new users and it seems to work. You may have to try incognito mode or force refreshing. Maybe you still have old JS in the cache.

After you create the user in the admin, can you tick "delete" next to the user profile below and save and then try to access the onboarding? Although both users who completed onboarding and not work for me.

natalieblackburn commented 5 years ago

I've been able to test this now, so I've created tbx-test-2 and tbx-test-3 who are in the level 1 and level 2 groups respectively. The workflow for their responses is working as expected, with level 1 still requiring staff moderation, and level 2 only needing submitting to the play store.

This is ready for your testing Madalina, let me know if it's clear enough for you test

madasan commented 5 years ago

This seems to work fine

madasan commented 5 years ago

This seems to have stopped working again. Any new users I'm creating get a blank screen when trying to log in. Works fine for users with admin status.

madasan commented 5 years ago

Ok I might have solved it, it looks like a language input field issue.

natalieblackburn commented 5 years ago

Thanks Madalina, closing issue.

natalieblackburn commented 5 years ago

Able to close this one as it's only relevant on staging, will leave the other issues open until deployed