Skip to content
This repository was archived by the owner on May 31, 2022. It is now read-only.

Clarification on when to use spring-security-oauth2-* vs this library #1562

Closed
pulse00 opened this issue Jan 18, 2019 · 2 comments
Closed

Clarification on when to use spring-security-oauth2-* vs this library #1562

pulse00 opened this issue Jan 18, 2019 · 2 comments

Comments

@pulse00
Copy link

pulse00 commented Jan 18, 2019

Since spring security version 5.x contains various oauth2 related features i'd like to ask someone with more insights: When should someone use this library over spring security 5.x?

What separates these 2 libraries? It's really hard to find facts on this.

We're migrating from spring security 4.x to 5.1 and use spring-security-oauth2 and are unsure whether to keep using it or migrate to the built-in spring security oauth2 features.

What's especially confusing is that the latest version of this library (2.3.4-RELEASE) has a dependency on spring security 3.2.10-RELEASE - being 2 major version behind the latest spring security version.

@jgrandja
Copy link
Contributor

@pulse00 Please see this announcement for more details.

For Client and Resource Server support, use Spring Security 5.x. If you require Authorization Server support, use Spring Security OAuth 2.3.x - until we support Authorization Server in Spring Security 5.x.

@pulse00
Copy link
Author

pulse00 commented Jan 21, 2019

@jgrandja thanks a lot - that announcement slipped my radar and google searches somehow :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

2 participants