-
Notifications
You must be signed in to change notification settings - Fork 4k
Home
N.B. this wiki is now writable only by committers. The plan is to move to gh-pages soon, so the content has gone to the main repo. If you want to make changes please send a pull request as normal (see guidelines in README).
OAuth for Spring Security provides an OAuth implementation for Spring Security. Support is provided for the implementation of OAuth providers and OAuth consumers. There is support for Oauth 1(a) (including two-legged OAuth, a.k.a. "Signed Fetch") and for OAuth 2.0.
Applying security to an application is not for the faint of heart, and OAuth is no exception. Before you get started, you're going to want to make sure you understand OAuth and the problem it's designed to address. There is good documentation at the OAuth site. You will also want to make sure you understand how Spring and Spring Security work.
You're going to want to be quite familiar with both OAuth (and/or OAuth2) and Spring Security, to maximize the effectiveness of this developers guide. OAuth for Spring Security is tightly tied to both technologies, so the more familiar you are with them, the more likely you'll be to recognize the terminology and patterns that are used.
With that, you're ready to get started. Here are some useful links:
-
For access to the binaries, use Maven (instructions here)
-
Source code is in github at SpringSource/spring-security-oauth.
-
You'll want to see OAuth for Spring Security in action, so here is a tutorial
-
Read a more detailed explanation in the developer's guide.
-
For more help and support, checkout the support links.