[BUG] Trouble signing into website

[jialincheoh]

@ManthanKeim , msawula@peddie.org <- this peddie teacher not able to sign into the website with the chrome browser

Hi,

I'm a NJ high school teacher and I've been busy during the week. (I had a heart attack at the end of Aug and I've been playing catchup since I returned). I hope to put in some time this weekend. I'm very happy that I seemed to have eluded the difficulties with Big Query authentication (assuming I follow the updated tutorial correctly). Two students from my school are also participating, but I'm not really talking with them. btw I never used Big Query before but I'm excited to. I do have a question about the charting libraries. I'm an Altair fan. Instead of Altair, Vincent is suggested. It also provides something of a wrapper/front end to Vega/Vega Lite. If you go to the Vincent github page (https://github.com/wrobstory/vincent), it hasn't been updated since 2016 and the author recommends you use Altair instead. So, you know, ...can I just use Altair?(!) I might, even if you say no!! I had trouble signing in to the website with my Chrome browser . I allowed permission for cookies for the site, but it still didn't work. I don't get an error, I just land on a previous tab I've had open after selecting a profile. Could profiles be a conflict? To sign in I ended up switching to Edge (since I never use it and I don't care what its settings are), but the Get In Touch button doesn't work with Edge. Should I try Firefox with a cookie exception for Iron hacks? Nice to hear from another person from NJ. What role is Stevens playing in this?

Thanks for reaching out.

ms

[ManthanKeim]

This seems to be an issue with the authentication of IronHacks with GoogleAuth; the current implementation is using GoogleAuth with Firebase; even if we host the platform locally, the app still reloads at the authentication page, so it has nothing to do with cookies.

this files is responsible for the authentication, so starting will this be a good start: https://github.com/ironhacks/ironhacks-app/blob/master/src/views/pages/login-page.js

@SantiagoTorres if you can look at it, we can definitely use some extra eyes on this bug, or if you can include your students.

[absol27]

@SantiagoTorres Looks like some of the google analytics trackers are getting involved in the login workflow. On Firefox - login works once I disable the option "Enhanced tracking protection is ON for the site", this is the default ad blocker(no 3rd party involved) provided by Firefox. I'm assuming this is the issue with other browsers as well - on Safari where I have a 3rd party ad blocker I get the error "Content blocker prevented frame displaying http://localhost:3000/login from loading a resource from https://www.googletagmanager.com/gtag/js?l=dataLayer". (Tested on prod site)

I'll work on finding out those extra tracker-related requests made by the server during login by comparing with and without the ad blocker to get a list. I can then isolate these gtag requests from the login workflow and then if needed I can add them at a later step.

[absol27]

Possible fixes from firebase docs, the issue is with the JS SDK opening an iframe to firebase domain that is cross-origin, the browsers and ad-blockers are blocking access to storage.

The simplest possible fix would be to change the current signInFlow from 'redirect' to 'popup', the popup doesn't trigger iframe like redirect does. Let me know if this works so I can push the patch @ManthanKeim @SantiagoTorres

[ManthanKeim]

e0a9c903cba7e797bb38a0f3b27d8402a0d986c9 processed