- This topic has 20 replies, 4 voices, and was last updated 12 years, 4 months ago by
walt.
-
AuthorPosts
-
support-octavioMemberHi walt,
Were you able to get the childbrowser approach to work out? Keep us posted on the outcome and if we can be of further assistance.
waltMemberthe childbrowser is working for the “passive scenario” federated authentication. I can catch the url when the Identity provider redirects away from the login page and parse it out.
Unfortunately, though this does work, it is not the preferred process. The goal continues to be to support the “active scenario” in which the token is passed with window.external.notify(). I am still trying to get that to work with cordova and xcode. If you guys come up with any ideas or suggestions about ways to handle that in mobione it is still a high priority objective for me.
waltMemberhi octavio and wayne,
I have been able to get the active scenario working in my app.
Here is the process:
1. I grabbed the access control toolkit for IOS from github. The info about the toolkit is here: http://www.wadewegner.com/2011/07/windows-azure-toolkit-for-ios-now-supports-the-access-control-service/2. I set up a cordova project including the childbrowser plugin in xcode
3. I imported the access control tookkit classes into the project
4. I added a new method to the childbrowser plugin call getToken that uses the access control classes to handle the whole federated authentication process.
5. I built my mobi project as a webpage and then hooked those files into the cordova project. I added a function to call the childbrowser.getToken method and save the returned token.
I have two questions:
1. The mobi output files were easy to hookup in cordova, with the exception of the custom CSS file. For some reason those styles are not being applied. I can move them, but I though I would ask first if there is a reason for this.
2. Any chance you guys could set something like this up on your server allowing mobiOne to call a getToken method or something like it? It was actually pretty quick to setup once I figured out what I was doing in xcode and it would huge to be able to use access control with mobione apps without the rigamarole of bringing it into xcode.
thanks!
waltMemberHi Octavio and Wayne,
I wanted to check in on this topic. Are you guys planning to include support for federated authentication in MobiOne?
It seems like there are a few plugins available now for cordova and it is definitely an in demand feature.
I would be happy to share how we set up the windows azure access control plugin if that would be helpful at all. We will be repeating this process with future apps and we would much prefer building apps from mobione if possible.
Thanks!
support-michaelKeymaster>I wanted to check in on this topic. Are you guys planning to include support for federated authentication in MobiOne?
Yes, yes, yes!
>I would be happy to share how we set up the windows azure access control plugin if that would be helpful at all.
All info welcomed. We can discuss here or via email; your call.
waltMemberThat is great wayne!
My xcode project is too big to attach to the thread. I can zip and email it — not sure if it will be helpful, but I guess it can’t hurt. What email should I send to?
I set this app up to work with windows azure access control. I used an example from this github project to get started:
https://github.com/deepukjayan/iOSAzureIntegration
I found this project to be much more helpful for setting up access control than the “watoolkit” that the azure team had up on github.
Since I started this project, windows azure has published a lot of new resources for ios integration. There is some great info here:
http://www.windowsazure.com/en-us/develop/mobile/tutorials/get-started-ios/
The access control was pretty easy to integrate with two manageable challenges to overcome:
The first was properly compiling the windows azure archive file (that needs to be included in the project) for the correct device architecture. I imagine though, this is straightforward for someone used to xcode, obj-c and ios, but I was thrown off for a while (app ran in simulator but not on device).
The second was setting up the native call from javascript so it would be triggered when the token needed to be refreshed and would pause the http requests until a new token was retrieved. There is probably a right way to do that — I simply set the http request to check if authentication is in progress and, if so, to cancel the request. then when the token is refreshed it retriggers the requests.
i am excited to hear you guys are including this in mobione. We love the speed of prototyping with mobione and as critical features like this get added in it means we can leverage that speed in more of our projects.
-
AuthorPosts