Great! So custom URL schemes work, and I can see the server URL with a padlock. 
Did you happen to test if TLS client authentication works as well?
—Joost

> On 09 Jun 2015, at 21:24, Aaron Parecki <[email protected]> wrote:
> 
> Here's what it looks like! It appears there are no hooks to do anything 
> except handle when the user taps the "Done" button in the corner. However, I 
> can set the callback URL to something like "exampleapp://auth" and that is 
> called in the AppDelegate as normal, so I should be able to use that to get 
> an access token and close the popup!
> 
> <oauth-test.png>
> 
> ---
> Aaron Parecki
> http://aaronparecki.com <http://aaronparecki.com/>
> 
> 
> On Mon, Jun 8, 2015 at 7:34 PM, Nat Sakimura <[email protected] 
> <mailto:[email protected]>> wrote:
> 
> I wonder how callback parameters are handed back to the calling app. 
> 
> Nat
> 
> 2015年6月9日火曜日、Leah Culver<[email protected] 
> <mailto:[email protected]>>さんは書きました:
> 
> This is the best news I've heard all year (if it does work well for OAuth).
> 
> On Mon, Jun 8, 2015 at 3:16 PM, Aaron Parecki <[email protected] <>> 
> wrote:
> Apple announced new changes in iOS 9 this morning. Not all changes got a 
> mention on stage. This one caught my eye as being relevant to this thread:
> 
> SFSafariViewController can be used to display web content within your app. It 
> shares cookies and other website data with Safari, and has many of Safari's 
> great features, such as Safari AutoFill and Safari Reader. Unlike Safari 
> itself, the SFSafariViewController UI is tailored for displaying a single 
> page, featuring a Done button that takes users back to where they were in 
> your app. (source 
> <https://developer.apple.com/library/prerelease/ios/releasenotes/General/WhatsNewIniOS/Articles/iOS9.html#//apple_ref/doc/uid/TP40016198-DontLinkElementID_26>)
>  
> I am curious to see what this actually looks like in iOS, but I'm guessing it 
> will show the address bar or have some other indication of the site the user 
> is actually on. This could be used for an embedded OAuth flow while still 
> being secure, and has the benefit of using the system cookies so that users 
> might already be signed in.
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "OAuth" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] 
> <mailto:[email protected]>.
> For more options, visit https://groups.google.com/d/optout 
> <https://groups.google.com/d/optout>.

-- 
You received this message because you are subscribed to the Google Groups 
"OAuth" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to