Many developers struggle with how to properly secure REST APIs. If you are like me, you followed a process from a trusted provider like Amazon, Google, etc. What if I told you there was a better way? It’s JOSE, a collection of open standards from the IETF that has strong library support. It’s also the basis of OAuth 2.0 and OpenID Connect. Let me show you how to make a highly secure API for today and well into the future built on the framework of JOSE.


Comments are closed.

Karl Hepler at 17:15 on 24 May 2017

Thank you!

Fascinating talk. Didn't know this stuff existed. As I'm now writing APIs that will exchange data between some of my own applications, I will definitely incorporate this into the process.

Great overview of JOSE tools and techniques. Glad I attended.

Joshua Smith at 14:58 on 25 May 2017

This was a good overview of JOSE. I have more questions now than I had before, but now I have a starting point for building my API with security.

Great overview of Jose

Mark Knapik at 10:32 on 29 May 2017

The information was great.
My concern is how well I'll be able to carry this back to my code and implement it. We got into a lot of heavy code.
I'm very glad the slides are provided here to help!

Sandy Smith at 15:50 on 6 Jun 2017

Excellent speaking style, and great content. Adam clearly laid out the need, the solution, and the different role each standard plays. It didn't detract from the talk, but I'd like to hear something of a differentiation of when full OAuth 2 is appropriate versus using JOSE standards like JWT.