Meteor package accounts-facebook doesn't work anymore - meteor

I have configured a Facebook login button using accounts-facebook package a while ago and it was working fine, but suddenly it's broken (its not working on the localhost as well as on the droplet giggorilla.co.uk ). I searched for the problem and as recommended I updated form meteor version 1.3 to 1.4, same for accounts-facebook I upgraded to 1.0.11. I double checked app id and secret key and the Facebook app is currently live and available to the public; however I am using http protocol on the environment server and on live server. This is the problem that I am facing:
Error in OAuth Server: Failed to complete OAuth handshake with Facebook. failed [400] {"error":{"message":"This authorization code has been used.","type":"OAuthException","code":100,"fbtrace_id":"HBMaCroDzQN"}}
packages:
accounts-ui#1.1.9
accounts-facebook#1.0.11
accounts-twitter#1.1.12
accounts-password#1.3.1
the facebook app config
the social services config
mup config

Related

How to enable Airwatch Tunnel in Xamarin.Forms WebView?

I have a WebView in my Xamarin.Forms app. Followed instructions here to integrate AirWatch SDK into my iOS App.
I have also added an SDK profile to the IPA via AirWatch console. The profile has been configured to use AirWatch tunnel when accessing a corporate resource.
However, I get a 403 (Forbidden) response when trying to navigate to the URL.
Am I missing any setup?

My custom Webpage for Oracle Cloud Application can be accessed from anywhere

I programmed (on JDeveloper Studio) a custom page for Oracle Cloud Application R13 and it is working like a charm. I deployed my customization on my Oracle WebLogic Server but I couldn't help to notice the website I created was HTTP and not HTTPS when I opened it from Oracle Cloud Application. On top of that, I also noticed I could access this custom webpage from anywhere (using any device) without any security verification or login as long as I use the same URL with its token.
I would like to know how to make my custom webpage's url not being accesible just with its URL and also make it HTTPS instead of HTTP if possible.
WebLogic Version: 12c
Oracle Fusion Application version: 11.13.18.10.0
JDeveloper version: 11.1.1.7.0
I believe this might have to do something with the WebLogic configuration, since I tested the same java project on Java Oracle Cloud SaaS Extension and it doesn't have this problem. Whenever I try to open that webpage from any other device, it asks me for login credentials. I am currently working with Oracle Java Cloud. (it is not the SaaS extension version) that's why I have this problem.
Have you configured security for your application in JDeveloper? If not then your page and application is considered public and not private.
As for HTTPS, weblogic server uses 2 ports one for HTTP and an other one for HTTPS.
Regards

Deploying asp.net web api to azure app service

Problem: after deploying my asp.net core web api to azure app service I can't get a response from the expected endpoint
Steps followed:
I have an api that works fine when serving from my local machine, developed using Visual Studio Code. (The code for that is here https://github.com/samrae7/blog-api FYI)
I followed the instructions in this video: https://www.youtube.com/watch?v=C8J_CRy2_XA to push the files up to Azure App services. Basically I used the VS Code azure app service extension to create a webapp on azure and push my files.
I can see my files have been pushed to Azure ( by logging in to the portal and looking) but when I navigate to the expected URL of my api, http://sams-blog-api.azurewebsites.net, I get 'site not found'. If I try to send a request to the expected endpoint (I append /api/resource as this is the path of the endpoints on my local machine) I get '404 not found'
So my question is what do I have to do to actually get my api up and running online after pushing the files to azure app service
Thanks
Your website is not accessible due to missing DNS entry. I check it using the mxtool
https://mxtoolbox.com/SuperTool.aspx?action=a%3asams-blog-api.azurewebsites.net&run=toolpage#
Please ensure that your url is correct.
The basic answer to this question was that I had not understood that you have to create a Database in azure for your deployed app to connect to, and you need to set the connection string as an env variable in azure so that it knows where to look, and you should also add code that automatically updates the database on launch.
This tutorial was what helped with that: https://learn.microsoft.com/en-us/azure/app-service/app-service-web-tutorial-dotnetcore-sqldb
I then hit another issue where the deployed app was still returning a generic 500 server error. By enabling 'Diagnostic logs' via the azure portal, and downloading the logs, I saw this detailed error: The configuration section 'httpProtocol' cannot be read because it is missing a section declaration referring to a piece of config in my Web.config. I deleted it (I don't need it for now) and that fixed the issue

upgrading wso2 api manager with custom url and https

https://docs.wso2.com/display/AM210/Upgrading+from+the+Previous+Release
I am following this to upgrade WSO2 API-M 2.0.0 to 2.1.0.
My 2.0.0 API-M has custom url configured and https certificates configured to map the url.
If i follow the migration as in the document , Will these things gets automatically migrated? Or will i have to manaully change the url in all the configuration files and also do the changes for https ?
I believe you are referring to [1] which is configuring custom URLs per tenant. If so you do not have to redo these configuration in the registry since the new deployment will be pointing to the same registry database as given in the migration documentation.
The changes done to configuration files in the file system, has to be re done in the APIM 2.1.0 pack. You can do a diff of the file system and do those changes.
The SSL certificates also have to be imported again. As an alternative, you can copy the keystores and truststores to the APIM 2.1.0 from the older version instead.
[]https://docs.wso2.com/display/AM200/Customize+the+API+Store+and+Gateway+URLs

Why pivotal returns only 404 for every application after I installed WildFly?

Every application that I run on pivotal server is now giving me a 404 although before installing WildFly (+executing standalone.bat) I didn't have any problem using the spring applications. Some applications weren't modified and after this update they wont work.
When I start pivotal and go on localhost:8080 it doesn't show home page for this server; it shows nothing, white page. Only when I start back WildFly I see its default home page.
Spring Tool Suite
Version: 3.7.3.RELEASE
Platform: Eclipse Mars.2 (4.5.2)
This is the problem:

Resources