Securing Rest-ful Web Services with OAuth2

Recorded at SpringOne 2GX 2012 in Washington, DC
One of the questions we get asked the most by developers and architects is: when and why would I use OAuth2? The answer, as often with such questions, is “it depends”, but there are some features of OAuth2 that make it compelling in some situations, especially in systems composed of many lightweight web services, which becoming a very common architectural pattern.

This presentation will not go into a lot of detail about the OAuth2 protocol and related specifications, but will attempt to show some of the key features of a system secured with OAuth2 and the decision points when choosing to build such a system.

7 Comments on “Securing Rest-ful Web Services with OAuth2”

  1. I wish this went into more detail about how to actually secure the WS with OAuth2, and not so much about how OAuth2 can be used to grant clients access to protected resources. What about actually securing the WS endpoints when a user account isn't needed, such as a REST endpoint for user-creation or other non-user related operation?

  2. Is there any way of getting a summary of this without having to go through 86 mins of talk?  A web site with slides and code would be thoughtful.

  3. if you attended springone2gx, you can access the slides now, you should have gotten an email to that effect. We'll have a page on SpringSource website soon where the slides will be available.

Comments are closed.