You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 5, 2022. It is now read-only.
The Spring Social demos indicate that using SocialAuthenticationFilter is the preferred way to integrate with Spring Security. Indeed I find it integrates better with Spring Security than using ProviderSignInController. However, the code in SocialAuthenticationFilter doesn't validate the state parameter from Social providers. Thus using it for sign-in appears to open up a security hole.
I'm using Spring Security 1.1.4 and have been able to perform authentication into a simple system with a state which the server requesting Social sign-in never created.
The text was updated successfully, but these errors were encountered:
The Spring Social demos indicate that using
SocialAuthenticationFilter
is the preferred way to integrate with Spring Security. Indeed I find it integrates better with Spring Security than usingProviderSignInController
. However, the code inSocialAuthenticationFilter
doesn't validate the state parameter from Social providers. Thus using it for sign-in appears to open up a security hole.I'm using Spring Security 1.1.4 and have been able to perform authentication into a simple system with a state which the server requesting Social sign-in never created.
The text was updated successfully, but these errors were encountered: