Skip to content

ResourceServerTokenRelayAutoConfiguration uses old Spring OAuth2 libraries #1975

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dsyer opened this issue Aug 16, 2019 · 4 comments · Fixed by #1976
Closed

ResourceServerTokenRelayAutoConfiguration uses old Spring OAuth2 libraries #1975

dsyer opened this issue Aug 16, 2019 · 4 comments · Fixed by #1976
Assignees
Milestone

Comments

@dsyer
Copy link
Contributor

dsyer commented Aug 16, 2019

There's probably a Spring Security 5.2 alternative that works.

@ryanjbaxter
Copy link
Contributor

@dsyer
Copy link
Contributor Author

dsyer commented Aug 19, 2019

Yes.

@ryanjbaxter
Copy link
Contributor

@rwinch @jgrandja any ideas?

@ryanjbaxter
Copy link
Contributor

The decision is to support both the legacy shim and the new implementation in Hoxton, then in the next major we will remove support for the shim.

@spencergibb spencergibb self-assigned this Oct 8, 2020
@spencergibb spencergibb transferred this issue from spring-attic/spring-cloud-security Oct 8, 2020
spencergibb added a commit that referenced this issue Oct 8, 2020
* Migrates token relay from spring-cloud-security.

Adds refresh token support.

Fixes spring-attic/spring-cloud-security#175

Fixes gh-1975

See spring-attic/spring-cloud-security#231
@spencergibb spencergibb added this to the 3.0.0.M5 milestone Oct 8, 2020
spencergibb added a commit that referenced this issue Oct 9, 2020
It moves it to spring-cloud-gateway-server

See gh-1975
spencergibb added a commit that referenced this issue Oct 16, 2020
It moves it to spring-cloud-gateway-server

See gh-1975
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants