Is it even possible for WP7 app to connect to service which is stored behind domain authentication?
I found Windows Domain Authentication on Windows Phone 7 article but it's not exactly what I'm trying to achieve.
Related
We're getting ready to rewrite an old native windows mobile application that accesses data through a VPN. We'd like the new version (.NET Windows 10 mobile application) to access data through web services that are protected by Okta. What is the best way to do this?
Thanks!
The best way to do this depends on how the web services are protected.
The main thing to keep in mind is that you don't want to store any secrets on the mobile application.
In an ideal world, these web services would be secured with something like OpenID Connect (OIDC), allowing you to authenticate against Okta (the "IDP") to get access to the web services (the "Relying Parties").
However, the real world is messy, where some web services are protected via SAML, OIDC, OAuth, custom headers, etc.
Without knowing more about your setup, my recommendation would be to build against OIDC, using a proxy server (or "API Gateway") as needed to secure your web services using OIDC.
One of my co-workers at Okta has written a sample iOS application in Xamarin that implements OIDC, I suggest taking a look at the ViewController.cs file in that repository.
I have a PhoneGap App running on WP7 that I would like to connect to a Windows Azure Mobile Service. However, in order for this to work in my testing using JSFiddle.net I had to add the JSFiddle domain to the CORS settings in the Windows Azure Mobile Service.
Why do I need to add domains to the CORS setting on the server when doing a simple GET?
Since the Mobile Service requires a key from the JavaScript code I don't see why I cannot open up this web service to any request that supplies the correct key but adding . does not seem to work. If this worked I could move on to testing the scenario on the Phone.
Am I missing something architecturally here or is this just a feature that no-one else is looking for?!
If you want to allow any domain to access your mobile service, you can add the * in the list of cross-origin resource sharing hostnames under the configure tab.
Notice that the application key is not secure. From the 'How to use an HTML/JavaScript client for Windows Azure Mobile Services' tutorial (emphasis mine):
Application key: A unique value that is generated by Mobile Services, distributed with your app, and presented in client-generated requests. While useful for limiting access to your mobile service from random clients, this key is not secure and should not be used to authenticate users of your app.
The takeaway is that you should not count on that key to secure your service.
Can we use simple java restful webservices to enroll the device under company apps in windows phone 8 devices.
I had tried with php and getting the proper requests but no luck with java my webservices are not even getting a hit from company apps.
Please suggest.
Yes we can use the simple java REST webservices for enrolling the device under Company Apps account.
I want to connect to remote machine using windows phone 7.5. Is there any inbuilt classes in .net for this.
For regular desktop application same can be done using ServiceController class. I am looking for the similar class for windows phone application.
ServiceController is used to control state of services on local or remote machine.
WP apps don't have a way of controlling remote or local services.
You would have to write SOAP or REST API for managing services and then connect WP app to those, but do make sure it is secured properly - you don't want to give access to service control to everyone.
Is there Messenger Connect API for Windows Phone 7 to use in Silverlight phone application to allow user authentication with windows live id and get a user consent to share profile data with my app? It all works great for PC desktop app or ASP.Net. I want the same experience for my users with the phone: login using windows live id and access the same data they can access on their desktop through a web site or desktop app. The backend is, obviously, multi-tenant, one database, many app users - everyone sees his own data based on his windows live id.
Nick Randolph demonstrated some interaction with the messenger api's here if you'd like to check it out.
Windows Phone 7 Beta with Windows Live Messenger Connect