I'm working with an application that was built and integrated to Facebook using the legacy connect auth:
https://www.facebook.com/login.php?api_key={appkeyhere}
Starting sometime the week of Oct 22, 2012, existing users who login to the app using the above URL get redirected to https://www.facebook.com/login.php?login_attempt=1 and have a blank white screen.
New users signing up to the app for the first time get redirected back to the application site.
I had the people who maintain the site check the deploy logs to see if there were breaking changes deployed to the pages that service the back end OAuth and they haven't made any changes.
Any ideas on where to start to try to debug this issue?
Only the current documented authentication flows in the Login documentation are supported - last week the last of the legacy endpoints (most of which were deprecated in October 2011) were removed - For desktop apps there's more specific documentation at https://developers.facebook.com/docs/howtos/login/login-for-desktop/ which covers the details
Related
I am trying to publish the Azure APIM developer portal - it is enabled for user/pass - authentication. We haven't customized it and are just trying to get it to work.
When I click publish and go to view the portal in a different browser I get the following message
"This is a home page of the Developer portal - an automatically generated, fully customizable website for publishing your API documentation where consumers can discover APIs, learn how to use them, request access, and try them out.
The content hasn't been published yet. You can do so in "Developer portal" section of your API Management Service in the Azure portal. Learn more."
When I go back to the Portal publish page, it resets to show "Publish" as if nothing has happened?
Are there any logs or anything I can test to get this to work?
BTW - the Legacy portal works 100%.
Thank you.
I have Created the APIM instance and added the HTTP Trigger API from Function App and published the developer portal by enabling the CORS option also.
Next, I have created the user and given all APIs Level access in the APIM Instance and opened both deprecated and legacy portal in different browser, logged in with the non-administrative user:
You can see logs of all activities in the Activity log of APIM Instance:
To see the Function App API imported in the APIM Instance, you have to add that API to the products subscribed by that user:
Published the developer portal again with new changes:
Activity Logs:
Result:
You can check each log activity from the Activity log to see complete details whether the operation publish or other is succeeded and how much time it took to complete.
Google is getting rid of less secure app access feature. I'm using smtp email service for my website's contact page. But after 30 May, 2022 this service will not work probably.
Is there any other way to give third party less secure app access to my Gmail account ..?
Can an app password solve this problem ..? I have doubts that setting app password will not give access either as google said this may not work for less secure app.
So is there any way to fix this so that the smtp email service works as it should ...?
TLDR:
I had a similar problem, I set up an App Password, and my email-sending piece of code is working fine again.
This video shows how to set up App Password.
Google's formal instructions for setting up an App Password.
Caveats:
Initially, Gmail had automatically turned off my less secure apps setting because I hadn't used that test account in several months. I turned it on, but since I saw the message that it'd be disabled by 2022.05.30, I went ahead and set the app password. This means my current setup has both less secure apps AND app password enabled in my Gmail account, though I'm only using the app password for authentication.
My program usually ran from within WSL2 on top of Windows 11. Even after setting up the app password, my code was returning a gaierror: [Errno -3] Temporary failure in name resolution error when running from within WSL2. I then tried running it straight from Windows 11 and it worked just fine. I now need to fix the networking issue causing this, but it doesn't seem to be directly caused by using app password.
I hope this helps.
Note: 2-factor authentication needed to be enabled before proceeding.
Less secure apps (https://myaccount.google.com/u/0/lesssecureapps) options is deprecated.
We can use apppasswords functionality provided by Google using following link.
https://myaccount.google.com/u/0/apppasswords
Use 16 digit code provided by google instead of password and that should serve as authentication token.
It can be done via 2 factor authentication and app password
I have a free openshift account and I created an app in July. After a month of inactivity i tried to use the app and:
-The web browser cannot resolve the url
-If I log in openshift I cannot see the app (the account is the same)
I'm not interested in finding the code because I have it on my pc, but I spent a lot of time in filling the database, is there anyway to restore it? After that, can someone explain me why my app has been deleted?
The OpenShift Online (Next Gen) environment is only in developer preview mode at this time. The FAQ on the main page at:
https://www.openshift.com/devpreview/
where you would have passed through when signing up states:
HOW LONG WILL I HAVE ACCESS TO THE ENVIRONMENT?
You will have access to the OpenShift Online (Next Gen) Developer Preview environment for 30 days, at which point your account will expire.
WHAT HAPPENS WHEN MY ACCOUNT EXPIRES?
Your account, applications, and data will be permanently deleted to free up resources for other users when your account expires. This means that you will no longer be able to log in to the web console, authenticate using the OpenShift CLI tools, or access your applications and related data.
CAN I CREATE A NEW ACCOUNT AFTER MY ACCOUNT EXPIRES?
If you're interested in trying the OpenShift Online (Next Gen) Developer Preview again, just complete the registration form after your account expires and we will provision a fresh set of resources for you as soon as they become available.
Created several app packages for a windows store app some time ago in order to show a client the progression of the application. Now I would like to load a much older version of the application onto the device, however PowerShell says that the certificate has expired and thus the application does not install. Is there a way to regen the certificate without recreating the entire app package and/or get around an expired certificate and just manually install the app on the device?
Everybody, We have released two WP8 apps that communicating with our backend server over HTTPS. We bought and installed the SSL certificate for HTTPS from Entrust. The 2 WP8 apps worked very well before May 30 but failed suddenly this week.The 2 WP8 apps reported HTTP 404 error this week. At the same time our Android and iOS apps that communicating with the same backend server over HTTPS have worked well before and are working well this week. It is weird. We suspect there is some change from Microsoft side on SSL,security policy, etc. But we, as formal WP developers,didn't receive any formal change notification from Microsoft and searched internet without getting any useful clue. Pls help and advice if you have experienced the same weird HTTPS issue with WP8 apps.By the way, I am contacting Microsoft now and haven't gotten any useful feedback yet. Thanks a lot!