I'm using quite a completely vanilla Fortify setup, sending email verification links is working with mailtrap. However, when I click the link in the mail, it opens the app and makes the user login, after which it doesn't redirect back to the verification url, but just shows the homescreen that tells the user to verify their mail.
The only way the verification link does work is when you paste the link in a tab where the user is already logged in. At first glance, to me it seems like a browser issue, that the browser doesn't preserve the cookies, but I've tried with different browsers (Safari, Chrome and Firefox) and all have the same issue. I run the laravel app locally through valet (or expose when I need to test API calls from a third party service) and dev environment on ubuntu 20.04, both have the same issue.
Related
I have a node js web app on Heroku that connects to the Spotify API through the Spotify authorization code flow. The web app works completely fine and allows the user to log in and the redirect URI works perfectly fine as well.
However, I purchased a domain from Namecheap that I linked to Heroku as a custom domain. Everything works fine, except for the fact that my custom domain somehow fails when trying to log in to Spotify. Keep in mind that if I go to the default herokuapp domain for my web app, the login works perfectly. But when I use my custom domain, it doesn't work. I made sure to add the custom domain as a redirect URI as well, so that isn't the problem.
If anyone could please help me figure out the issue, that would be greatly appreciated.
This link shows a short video of the problem:
https://www.youtube.com/watch?v=oJjX5q43Ve0
The first site in the video is the default herokuapp webpage, which works flawlessly. But the second site, which is my namecheap custom domain, just brings me back to the main login page even after signing in through Spotify.
When I try to login to my heroku account in a web browser, the page just refreshes and does nothing.
If I give it wrong credentials then it shows the error message.
I tried using cli but it opens the browser and gets stuck on the same loop.
Used other browsers both on windows and android, resetted the password, used vpn, asked a friend, all results in the same refresh thing.
Asked the account-lockout heroku email id, it plain out autorejected my mail because the mail has a '.' inbetween.
Heroku Mail id
firstlast#gmail.com
Gmail id
first.last#gmail.com
I looked up other links over here and on other sites as well to no avail.
If I use help.heroku.com and then goto dashboard, it shows the loading animation and then goes back to the login page
Any help on this would be seriously appreciated
Working with Laravel 5.2
Using SammyK/LaravelFacebookSdk
I have an web application witch users can vote in each category once so before they can vote they have to login to facebook everything working fine until it comes to the redirect the user to the page with message like thanks for voting here is the application on the internet Here
Now whenever the user click on vote I get different responses on my PC on
chrome everything working OK
on Firefox and other devices Not working
Whet happens is is the voting done successfully but the redirect back not
it go to this URL
https://www.facebook.com/v2.9/dialog/oauth?client_id=139382809958016&state=d517376c10784f6b5f718112a7c49b83&response_type=code&sdk=php-sdk-5.5.0&redirect_uri=http%3A%2F%2Fsatfestival.net%2Ffacebook%2Fcallback&scope=email%2Cuser_events#_=_
and redirect back to this URL
satfestival.net/facebook/callback/?code=AQApHGQa5LtqLSv75bq8V6QA_6I9ivmKJ07kcO3aYY7pCmSIYoPu8lzrZhRSGYXg7weiOgIa5c1vKDchsbVepn0-LH9rh1kUKgpcJ71DFtYqbZLMLfEYD1DJWmqyqoFS_RL03b2IhZx62LP8NyepCZ0zTn8auxzGN2-jhtZ-YHVFPuGlJI31UnCc7ymhCXu1Zie8hMxp38z5CvPrhE5lDEEQjDgXqz2o45XTsOR3WaJfbEx51yscGx4SFr0Gtl6DKSTXol-3tkqkMZ3JhP7-JXk7RHwj1c3PhDTwXcgc6c8gq4qOMSwaR_EWnZtn8vX5ICc&state=d4e6fd2949abda8f85810e36a4a3fc35#_=_
and again redirect to the first URL and back to the second URL and so on.
Here is a screen shot of the Facebook Client OAuth Settings
if someone like to see the controller I will provide the controller too.
I am using jekyll-google-auth to secure this website. Visiting the site should prompt the user to authenticate with google, and if they are in my company domain, they should get access to the site.
I have the google app set up, my dyno is up and running, but when I visit the site and click "allow" (or "deny" for that matter) I am not redirected to the site, instead it seems to refresh to the same auth page. I can click "allow" or "deny" indefinitely and never get to the site.
My redirect uri in my google app settings is:
http://dash.fractalhardware.com/auth/google_oauth2/callback
The command jekyll-auth new is supposed to run through setup for you, but it failed for me. It spit out an error when I entered my domain when prompted for GOOGLE_EMAIL_DOMAIN. So I went into the heroku settings and just added it manually in the config variables. I read through the code for the jekyll-auth command and confirmed the setup should've been complete. I don't think that's related to the auth problem but it's the only obvious hiccup I've come across.
Any idea why the oauth page seems to refresh/redirect to itself instead of authorizing the user and showing the site?
Thanks,
Dave
I'm using a webview to host a log in page that redirects to an ADFS server to offer single sign on. This works on 10.9, but I noticed for OSX 10.10 I am able to get to the point where the ADFS server will present an http authentication challenge, the webview will show the default dialog to enter credentials, but after entering the credentials I never see the expected redirects that eventually allow the single sign on process to complete. Even if I cancel the webview prompt to login, I never receive a didReceiveResponse message (in the WebResourceLoadDelegate protocol).
Does anyone know of any changes in the webview for 10.10 that may cause it to stop sending/receiving requests/responses like this?
Update: It looks like this issue is a problem with WebViews and HTTP Basic Authentication in general. I have created a simple mac application with a single web view, and pointed it to a apache web server with a folder protected by an .htaccess file. While the app is able to successfully view the actual web page after the user enters their credentials in the login prompt on 10.9, on 10.10 this fails in the same manner as described above.