I have a problem with facebook integration in meteor with a 404 on the last step of authentication. When i click on the login with facebook button (accounts ui), it pops up the facebook u/p screen and i enter details in correctly, fb then tries to send the following:
http://localhost/_oauth/facebook?close&code=XXXXXXX
Which results in a 404 page does not exist.... any ideas?
Update not that it should matter: i am using meteor on windows.
Update it seems that the problem is with the port. Both google and facebook are returning back to localhost and not localhost:3000 the default meteor port.
Does anyone know how to set that it redirects to port 3000 and not :80. If i start meteor --port 80 it works fine.
Thanks
Related
I have a Next.js website deployed to AWS Amplify.
To log into this website, the process goes like this:
The user access another app and log in using e-mail and password
This app makes a post request to my website's api passing some user data
My website's api validates the data, generates a cookie and redirects the user to the home page
This process works fine localy in development and even in previously deployed websites that use the same code, but is not working with this new one.
I don't know if I'm reading into it right, but it seems like this new website is fowarding the redirect as a POST request instead of a GET. The image below shows how it should be (left, the correct way) and how it's currently going (right, the wrong way).
To redirect the user to the home page I simply use res.status(302).redirect("/").
So I have email link signin (password less) working for iOS and Android, but if a user requests the email and then opens it on a web browser, they see this message:
Error encountered
{"error":{"code":400,"message":"API key expired. Please renew the API key.","errors":[{"message":"API key expired. Please renew the API key.","domain":"global","reason":"badRequest"}],"status":"INVALID_ARGUMENT"}}
I need them to click the link using their mobile device in order for the authentication to work, but ideally I could provide a more graceful message here that tells them to open the link on the mobile device. Any ideas?
I've now got this redirecting to my own website. Long story short - for some reason my Firebase hosting site was not configured properly and thus this authentication url was not being handled as it should. Fixable by recreating hosting site or just creating an additional site under hosting and using that for the email action url.
What I did was:
Create an Additional Site on Firebase Hosting. I made it additional so I wouldn't have to worry about messing with the Dynamic Link setup that is currently working on the default site.
Then under Authentication > Templates in the Firebase console, I changed the action url to use the new site but still have the (__/auth/action?...) path after the domain.
Now, when this url is accessed via a desktop browser, the user is redirected to the continue url (specified in the action code settings of the mobile app) and I display what I want on this continue url.
I noticed that in my Google API console, Firebase created a new Browser key and that it is being used whenever this auth link is clicked. Perhaps this was the issue all along. I wonder if I somehow restricted the wrong key. Anyways, if you run into a similar issue, check your API keys and their restrictions and/or just create a new additional site in Firebase hosting and use that.
I am new to HTTP requests and I am trying to send a GET request to the login page of Oracle Apex Developer which is on a private company server.
I think the browser uses cookies which can expire because when I try to access the URL in the browser (substituting the servers IP as host name), then I first get a prompt to enter my company SSO username and password. This works fine and I can then get the page in the browser. I am trying to replicate this in python but nothing is working for me. I have even tried using HttpNtlmAuth but to no avail.
I could not see anything in Chrome network tab to indicate what the browser is doing and I have tried to simulate most of the HTTP headers in my python code (see picture below)
Here is what the browser was doing once I entered my username and password to get the 200 status code:
Any ideas what I am missing here?
Thanks
I recently renewed my domain name after it expired. However, when I try to view my website, a login box popups.
This is new. I tried putting in my wordpress admin username and password all to no avail. Infact I get a '401 Authorization Required' error.
I have been at this for some days now. I contacted my hosting provider. They said they could view my website and that everything is fine. They however instructed me to clear my browser cache and cookies, which I have done. Still, the problem persist.
I tried viewing the site with an IP proxy site and truly I could see my website without any errors or login pop up box.
How do I solve this problem?
A 401 request usually means that your client (e.g. your web browser) is not able to authenticate itself with the server therfore cannot view the resource.
You have cleared your cache and cookies and you're prompted by a login
box, following this a 401 error appears. The site is viewable from
proxy.
Things to check,
Flush your DNS
Are the login details correct? its possible to get this error from incorrect logins
Check the URL for errors, make sure you're using the intended url
Try deactivating your wordpress plugins if problems still persist
Any further information you can provide, including images would help a lot.
I have a Java Servlet web application deployed to Google App Engine.
It has a login page and when the user is successfully logged in, it navigates to the Home servlet.
The http site stopped working from today's redeployment/upgrade to the app due to the code 302. And it only occurred on the computer when the redeployment/upgrade was performed.
When trying the app with the http protocol, it threw http 302 on the Home servlet. Then it navigated back the login page.
When trying with https protocol, however, it navigated correctly to the Home servlet on http 200.
Not sure if this is a GAE setting issue or a browser thing (I am with firefox)?
EDIT: I realised that the http site worked fine again if I cleared the cache on firefox. But when I accessed the https site, http stopped working again due to the same 302 issue.
302s are not necessarily "failures"; They are redirects. When a user goes to log in, are you redirecting them? Perhaps from an http to an https login page? And when they log in, are you redirecting them back to the original page?