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?
Related
I have a website which is currently live and uses Azure B2C to manage user authentication. The site has been so successful that I have decided to build App (IOS and Android) versions of the site using Xamarin.
My 2 questions are:
Can I use my existing Application Registration in B2C to authenticate both my MVC and Native Apps. If so is this done via the Allow Public Client Flows Radio button under the Advance Settings Section of the Authentication tab in Azure B2C? Will turning this from No to Yes impact the running of my registration for the website (as the system is live with thousand of users I am very wary of making updates to B2C Settings.
What is the best way for testing changes to Azure B2C? Is there an easy way to create dev environments that can then be flipped to live, switching out the live version with the dev environment?
Any help will be gratefully received.
J
Can I use my existing Application Registration in B2C to authenticate both my MVC and Native Apps. If so is this done via the
Allow Public Client Flows Radio button under the Advance Settings
Section of the Authentication tab in Azure B2C? Will turning this from
No to Yes impact the running of my registration for the website (as
the system is live with thousand of users I am very wary of making
updates to B2C Settings.
It's not recommended to use the same app registration in this case.
Please see the differences between public client and confidential client applications.
Confidential client applications are safe to keep application secrets while public clients not. If you use the same app registration, there is a conflict in keeping application secrets. And using the same app registration for multiple applications will make permission control more difficult.
So in this case, it's recommended to create a new app registration with Public client/native platform.
Turning Allow Public Client Flows from No to Yes doesn't mean to change it to native app type.
You could set "allowPublicClient": true, in the manifest file.
What is the best way for testing changes to Azure B2C? Is there an easy way to create dev environments that can then be flipped to live,
switching out the live version with the dev environment?
Creating a new app registration will not affect the use of your web application.
We are currently trying to add OAuth2.0 for authentication into an existing Adobe AIR mobile app for a client. We are trying to carry this out by using this library https://github.com/charlesbihis/actionscript-oauth2 from this article.
We have tried using instances of the 'StageWebView' class and the Feathers UI 'WebView' class to display the authorization prompt page within the mobile app itself.
When we publish the app locally on our development PCs, the whole process works ok. However, as soon as it is published to our iPad(s) for testing, it is almost as if some security setting stops the "embedded" website from communicating with to the server.
As the website we are trying to communicate with is a https:// address, I'm assuming that this might be causing issues, but I can't confirm this.
Has anyone out there found themselves in a similar situation?
Thanks,
Dave
Is this possible to authentice iOS Mobile App with Windows Azure Active Directory(AD) with utilizing mobile web services of Azure.
Basically iOS App should be login with only the Windows Azure Active Directory(AD)
I found one third party library
https://github.com/MSOpenTech/azure-activedirectory-library-for-ios/
but not sure whether this is secured or should be used or not
Microsoft Open Technologies (MSOpenTech on Github) is Micrsoft's official approach to helping open source communities both on and off the Microsoft platform. This should give you confidence in the legitimacy of the code on Github. See here for more details: https://msopentech.com/
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.
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.