My ASP.Net MVC3 web site that logs into Facebook is no longer working after moving to an Azure based cloud project. I am using the Azure SDK 1.6 and fail during the the OAuth steps.
I had a working site that ran locally at http://localhost:1200 which matched the Application Url setting that was registered for the application on Facebook. Now when I try to start the project in debug mode, it goes through the Azure emulator which maps the web site (role) to http://127.0.0.1:82/. I've tried updating the Facebook app url to the same address but it fails.
I've been investigating this and I've noticed that the Azure emulator automatically creates on the fly a new IIS web site and employs a load balancer for its created virtual IPs for the individual projects within the cloud solution. Is there a way to get a project to debug successfully and still talk to Facebook when running the Azure emulator within Visual Studio?
Any insight is greatly appreciated.
I would not use localhost for Facebook applications.
What I did, I had registered my real domain in Facebook (such as myapp.com)
Then I created a record in my hosts file (Windows\system32\drivers\etc\hosts)
127.0.0.1 dev.myapp.com
which is sub-domain of my production domain, so it's allowed by FB;
And then I used dev.myapp.com as callback address for Facebook; I also setup Visual Studio to run http://dev.myapp.com:anyport on start application debugging.
Related
Published applications can't open Universal Windows Applications (UWA). Edge has changed the authentication to a UWA method for sync authentication. Given this we cannot get Sync to work as we cannot authenticate. Any ideas?
I have a ASP.net MVC project hosted in Azure and with Azure AD authentication
Everything works fine when I publish my project, but after a while when trying to login again, I get the famous login loop.
If I restart the app service, everything works fine for a while again...
I have read many posts and blogs regarding this subject and I think I have tried evertything.
Reply url and keys are correct both in Azure and web.config
Applicaton is forced to https
I have tryed the katana cookiesaver fix.
Reply url other than root
Other suggestions?
I'm new on ASPNet MVC 5, I'm confused about IISExpress. I am developing intranet site and I use windows authentication. After publish and run site on IIS I saw that authentication pop-up which not came on IISExpress. Why there is something like this? After searched about preventing that pop-up I saw that I have to add site to trusted website, however, I didn't do this for IISExpress, did IISExpress do it for me automatically? In addition to this I have a problem about EWS Managed API on IIS
IIS Express is a process that runs in the context of the currently logged on user, meaning you. Your account usually has enough (or too much) permissions to access files and other resources.
The 'big' IIS uses different user accounts to run your application, these accounts have limited permissions and may not have access to files and resources. If IIS can't access a file with its normal process account, it needs a different account to access that file and asks for one in a popup.
I am trying to connect to VSO using oAuth.
First step is to register our app and configure a call back url.
I am creating a console application to test the connectivity.
Please let me know how to configure the callback url.
Firstly, please take note that: Right now, it is only supported to register web application, it is impossible to register a console app.
So, you need to have a web app first, you can download and use this sample project for a quick start: https://vsooauthclientsample.codeplex.com/
After you download the app, open it in VS2013 or higher, right-click it in Solution Explorer and select Publish.
On the Publish Web page, select Microsoft Azure Website option to publish that web app to Azure.
Then, the web app is published to Azure with the URL similar to: https://vsodevabc.azurewebsites.net
And when you register this web app, you can set Application Website and Callback URL to be the followings. (note: the callback URL should be https://yoursite.azurewebsites.net/oauth/callback, where "yoursite" is the name of your Azure web site)
When using VSO (now called Team Services) with oAuth2.0 you do have to provide callback url endpoint that Microsoft's Team Services can call directly. So you need to have your application's callback url endpoint published such as publishing to Azure or Aws or any hosting provider that will allow you to have publically accessible url. In the FAQ under Team Services Rest API, there is mention of this approach for debugging purposes:
Visual Studio Team Services does not allow localhost to be the hostname in your callback URL. You can edit the hosts file on your local computer to map a hostname to 127.0.0.1. Then use this hostname when you register your app. Or, you can deploy your app when testing to a Microsoft Azure website to be able to debug and use HTTPS for the callback URL
Visual Studio Team Service's Rest API oAuth
On my development machine (which has the Quickbooks SDK installed) I can connect and interact with QB just fine; the standard workflow of granting access to the external app from w/i QB works. However, on my production machine I get various and sundry errors:
Can't start QB.
Can't start QB because it's already running.
Can't open more than one company file.
The dev docs lead you to believe that the app must be signed while elsewhere I've found examples where you could run an un-signed example app. So what is it? If signing isn't strictly required then any clues as to why I can't get this to work?
Production Machine
QuickBooks Pro 2011 Release R9P (US)
Our installed, OOB, Silverlight app
Dev Machine
Quickbooks Premier Contractor Edition 2010 Release R13P (US)
Silverlight 4 using COM/C# to connect to QB
Quickbooks SDK 11.0
As I've said, the dev machine works as it should. On the production machine we've tried every combo of not having QB open, having it open but no client file open, having it open and a client file open and we'll get one error or another right at the point we're trying to open a connection. Also, our app never shows up in the integrated applications settings page (but it does show up on the dev machine's QB). We've tried both admin and non admin.
No, you DO NOT need to sign your apps.
You didn't provide anywhere near enough information for us to really give you a solution.
Did you check your SDK logs?
What version/year/edition/country of QuickBooks?
Are you building for the Web Connector, or using C#, or VB .NET, or...?
If you're using the Web Connector, what do your Web Connector logs look like?
Are you logged in as the QuickBooks admin user?
Is QuickBooks already running?
Is there another QuickBooks company file already open?
Did you revoke permission from the integrated application?
If you expect answers, you have to post some details.
It's a Silverlight app with full trust. It looks as though it was something with SL itself. Once we upgraded to SL5 it worked fine.