Hi I had managed to let FB log in work, but after I changed "Valid OAuth redirect URIs" setting in FB and than change it back again. Login is not working anymore.
My server shows:
Error in OAuth Server: Failed to complete OAuth handshake with Facebook.
{"access_token":"*******...",
"token_type":"bearer","expires_in":5183894}
Any ideas? I heard open a new FB app may work, but it can't be like this every time. Thanks you!
This should solve the problem, edit the meteorite packages file and replace it with:
accounts-facebook#1.1.0
facebook-oauth#1.3.0
or update meteor version, works for me
Related
When app is running without nginx then Flask forms work fine. But when I use NGINX then i get "{'csrf_token': ['The CSRF tokens do not match.']}" error every time I try to submit the form.
What could be an issue?
I have tried:
to clear all the cookies from the browser.
submit the form while accessing an app in incognito mode.
reviewed all of the forums in stackoverflow that are related with this issue.
Nothing helped. What could be an issue here?
I found out the answer in this article: https://nickjanetakis.com/blog/fix-missing-csrf-token-issues-with-flask
Appearantly Flask does not loke (cookie likewise) to use IP addresses as SERVER_NAME parameter. So at least set it to localhost.domain or something similar and everything will be ok :)
I have a personal website: https://www.${DOMAIN-NAME}.web.app (advertising my real site may annoy some people)
This web app is working fine on my devices. I sent this link to my friend and it's showing him "ERR CERT COMMON NAME INVALID" error page. He is on a very secure computer.
Here is a screenshot of the error page:
I found one solution to this along with a process to recreate this error page. I went on a new device that has never visited my web app. Then, I wrote http://www.${DOMAIN-NAME}.web.app ("http" here) and got this error page. Changing from "http" to "https" here doesn't help. However, I solved this by closing the tab, and writing https://www.${DOMAIN-NAME}.web.app on a new tab. This immediately establishes the green secure lock.
However, this didn't help my friend. Is there something that I don't know that's causing this issue? I'll await any helpful answers. Regards,
You cannot add a www. in front of a Firebase Hosting .web.app domain. That's why you're seeing invalid cert. Try just https://${DOMAIN-NAME}.web.app.
I have been trying to enable HTTPS login on alfresco but it seems to be a challenge to get it working.
I can access my website via HTTPS and get the login page, but when I login with the correct credentials I get the following error :
Something's wrong with this page...
We may have hit an error or something might have been removed or deleted, so check that the URL is correct.
Alternatively you might not have permission to view the page (it could be on a private site) or there could have been an internal error. Try checking with your IT team.
If you're trying to get to your home page and it's no longer available you should change it by clicking your name on the toolbar.
I must login in HTTP then refresh my HTTPS page to be connected in HTTPS.
I have already seen what the offical doc says and tested it but it didn't work.
Has anyone an idea on how to fix the problem ?
Thanks
The alfresco.log / catalina.out should tell your more.
Where / how did you set up https? Have a a reverse proxy like nginx or apache in front of the alfresco tomcat?
If the log says something like "CSRF Token Filter issue" then you need to set share.host / port / protocol in alfresco-global.properties as seen from the browser.
I'm trying to retrieve user and password from the url http://user:password#domain.com using nginx but I cannot find these variables name in nginx documentation or google.
Is there anyway to achieve this or to get the url that the user has truly typed in his browser ( i.e. http://user:password#domain.com ) ?
Many thanks for your help!
Ok, in fact my problem was related to the fact that my browser (FireFox) seems to not handle request like http://user:password#domain.com anymore.
I have tried curl and nginx successfully pass user and password to php.
#user1723580 The basic authentication in URL is working fine in Firefox event on the latest Nightly version.
Most answers to this questions suggest to make sure your Twitter app is setup as a "web app" and not a "desktop app"... in the current Twitter dev site... I do not see this option.
I also made sure to provide a callback URL when first setting up my app.
Any thoughts?
Use the callback url for your app. For local development, you can use 127.0.0.1 or proxied address like http://www.localhost.com. Then, error will disappear. Thanks.
The API returns a 401 when the OAuth tokens you've provided are revoked/invalid or any time you attempt an action for which you do not have access. For example, if your application is read-only and it attempts to post a tweet, a 401 will be returned.
Twitter does provide an error message and Twitterizer will return that to you when it can. It is in the ErrorMessage property of the response.