This doesn't seem like correct behaviour for ASWebAuthenticationSession?

I just wrote code for our app to use ASWebAuthenticationSession for 3rd-party authentication (in particular, YUBIKEYS WOOHOO). Our app registers a URI scheme of x-com-kithrup for launch services events, so I used x-com-kithrup-yubi for ASWebAUthenticationSession.

Only, I didn't change the back end, so it still redirects to x-com-kithrup://success on a successful login. And... ASWebAuthenticationSession is still calling the handler when it gets a URL with the x-com-kithrup URI, instead of the x-com-kithrup-yubi URI scheme.

Up vote post of kithrup Down vote post of kithrup
352 views
Posted by
kithrup
Reply
Add a Comment

Replies

It seemed so wrong to me that I wrote a test application, and FB13152737 with it attached.

Posted by
kithrup
Post not yet marked as solved Up vote reply of kithrup Down vote reply of kithrup
Add a Comment