Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Potential Method Bug: State Token potentially lost when new a Oauth window opens on iOS mobile browsers #16

Open
michaelangeloio opened this issue Dec 16, 2020 · 11 comments

Comments

@michaelangeloio
Copy link

michaelangeloio commented Dec 16, 2020

Hi FoF! Hope everyone's doing well!

While testing FoF Oauth on mobile, specifically iOS 14, I believe there is an error. Here's a link to a video demonstrating what happens.

I'm thinking it may be an exception that's raised when Flarum tries to compare tokens because the token is lost during a new window launch. Could be wrong though!

Whoops! There was an error..zip

Thank you :)

Michael Angelo Rivera

@michaelangeloio
Copy link
Author

You may have to copy and paste those URLs to your browser!

@clarkwinkelmann
Copy link
Member

I'm unable to view the video. Can you enable public access?

It's probably not a good idea to share a Facebook access token here. Though it will probably have expired by the time anyone can test anything.

This kind of error can happen if your URL in config.php is invalid and that a redirect is followed at some point.

It would be very odd if it doesn't happen on all browsers but only mobile.

@michaelangeloio
Copy link
Author

@clarkwinkelmann should be expired soon (I think, lol). I've edited the URL of the video, can you test if it works?

Also, the login works (for other users as well) for all devices except mobile (iOS specifically). You can also test the same error if you have iPhone at https://sheetscience.io

@clarkwinkelmann
Copy link
Member

Unfortunately I don't have any iOS device, and I don't see any obvious issue just by looking at the video.

Let's wait for another FoF member to chime in. Not sure if anyone's got Apple products to test.

@katosdev
Copy link

@michaelangrivera i have an iPhone 12 pro on iOS 14.2.1
To assist me in testing this and confirming, please can you:

  • confirm what iPhone model you are using
  • confirm what iOS version you’re on
  • Confirm if this same error is present on google chrome (or another browser) on your mobile.
  • Provide an invite code (preferably 2) so that I can test both normal and OAuth login.

Kind regards
Phil

@michaelangeloio
Copy link
Author

@katosdev hi!
My phone is iPhone 11 running on 14.2.1, the other user I had test it was on an iPhone 12 Pro using 14.2.1 when testing. I can have others with other models test as well.

The same error is persistent across three browsers on the iPhone- Safari, Chrome, Firefox. I've tested all 3.

X3I8I6T3 is one I have generated for you.
BOBB0D1O is another I have generated.
Would you like one that "activates user" as well?

Thank you,

Michael Angelo Rivera

@katosdev
Copy link

@katosdev
Copy link

Issue not present when PWA extension is disabled, suspect that the CSRF token is not being passed through properly for the OAuth.

Further testing is required on my local host but I may have a potential fix.
This appears to be a common OAuth issue, looking at other providers.

@michaelangeloio
Copy link
Author

@katosdev Awesome! Just let me know if you need any more assistance from my end!

@michaelangeloio
Copy link
Author

@katosdev Any ideas or workarounds that you're thinking of?

@DavideIadeluca
Copy link
Member

@michaelangeloio Is the issue you were describing still happening on the latest version of fof/oauth ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants