No, no especial need at this time. It was more out of curiosity, you guys did a great work...and quick too!
I mean, It's just nice for a new project in Swift to be able to work with Swift libraries instead of having to mock with bridging files and @objc annotations. But again, not a strong reason at this time. I did find https://github.com/p2/OAuth2 which is Swift and adheres to the Best Practices document by using SFSafariViewController for OAuth, so since someone else is working on it I will not be volunteering to re-invent the wheel :) Keep up the good work! On Sat, Apr 2, 2016 at 6:44 AM, John Bradley <[email protected]> wrote: > The current iOS version works just fine with apps written in Swift. > > I don’t know that there is a compelling reason to support two code bases > on the same platform as long as the SDK supports all the development tools. > > Other than as an example, do you have a reason for needing it in Swift? > > At the moment the focus is more on expanding the functionality. > > Adding options for creating and validating JWT/id_tokens, JWE encryption > support , Token binding for refresh tokens that can use the TPM for > security, Application Configuration via a EMM (AppConfig) , Alignment > with the the GSMA Mobile Connect SDK so that developers don’t wind up > needing one SDK for Azure and another to support the Mobile Network > Operator openID service. > > Let us know what directions are important to you. > > Regards > John B. > > > On Apr 1, 2016, at 10:39 PM, Andy Zmolek <[email protected]> wrote: > > > > > Any plan to bring the libraries to more ?young? languages like Swift > in iOS and Kotlin in Android? > > > > Are you volunteering? > > _______________________________________________ > > OAuth mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/oauth > > _______________________________________________ > OAuth mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/oauth > -- -- *Eduardo Gueiros* *Director, Mobile B.U.* | Jive Communications, Inc. jive.com | *[email protected] <[email protected]>* <http://www.facebook.com/jive.communications.inc> <http://www.twitter.com/getjive> <http://goplus.us/jive> <http://www.youtube.com/jivetalks> <http://www.linkedin.com/company/jive-communications-inc>
_______________________________________________ OAuth mailing list [email protected] https://www.ietf.org/mailman/listinfo/oauth
