-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Revise Spring Integration security in favor of Spring Security Messaging #3897
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
Labels
Milestone
Comments
artembilan
added a commit
to artembilan/spring-integration
that referenced
this issue
Oct 14, 2022
Fixes spring-projects#3897 Spring Security has deprecated `AccessDecisionManager` and all its infrastructure in favor of `AuthorizationManager` * Deprecate and AOP `ChannelSecurityInterceptor` and all its infrastructure, including `@SecuredChannel` and respective XML configuration. The `AuthorizationChannelInterceptor` added to respective channels for security or configured as a global channel interceptor fully covers the previous AOP configuration * Fix deprecation warnings in other tests with security
artembilan
added a commit
to artembilan/spring-integration
that referenced
this issue
Oct 17, 2022
Fixes spring-projects#3897 Spring Security has deprecated `AccessDecisionManager` and all its infrastructure in favor of `AuthorizationManager` * Deprecate and AOP `ChannelSecurityInterceptor` and all its infrastructure, including `@SecuredChannel` and respective XML configuration. The `AuthorizationChannelInterceptor` added to respective channels for security or configured as a global channel interceptor fully covers the previous AOP configuration * Fix deprecation warnings in other tests with security
artembilan
added a commit
to artembilan/spring-integration
that referenced
this issue
Oct 17, 2022
Fixes spring-projects#3897 Spring Security has deprecated `AccessDecisionManager` and all its infrastructure in favor of `AuthorizationManager` * Deprecate and AOP `ChannelSecurityInterceptor` and all its infrastructure, including `@SecuredChannel` and respective XML configuration. The `AuthorizationChannelInterceptor` added to respective channels for security or configured as a global channel interceptor fully covers the previous AOP configuration * Fix deprecation warnings in other tests with security
garyrussell
added a commit
to artembilan/spring-integration
that referenced
this issue
Oct 17, 2022
garyrussell
added a commit
that referenced
this issue
Oct 17, 2022
* GH-3897: Deprecate `ChannelSecurityInterceptor` Fixes #3897 Spring Security has deprecated `AccessDecisionManager` and all its infrastructure in favor of `AuthorizationManager` * Deprecate and AOP `ChannelSecurityInterceptor` and all its infrastructure, including `@SecuredChannel` and respective XML configuration. The `AuthorizationChannelInterceptor` added to respective channels for security or configured as a global channel interceptor fully covers the previous AOP configuration * Fix deprecation warnings in other tests with security * Fix language in docs Co-authored-by: Gary Russell <[email protected]> * * Remove `forRemoval` attr from `@Deprecated` markers for Security classes: looks like to mark `@Deprecated` and even `@SuppressWarnings("deprecation")` don't silence warnings on compilation Co-authored-by: Gary Russell <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
AbstractSecurityInterceptor
(and supporting API) is deprecated in Spring Security now.Consider to deprecate
ChannelSecurityInterceptor
in favor ofAuthorizationChannelInterceptor
from Spring Security Messaging.With that move we probably will deprecate a
@SecuredChannel
and all the AOP infrastructure we have inspring-integration-security
.The fix depends on the spring-projects/spring-security#11915 which will bring for us a
postReceive()
security contract.The current
receive()
AOP interceptor does not make too much sense since there might be just no a staticSecurityContext
to auth against.The
postReceive()
phase may be already populated from the received message viaSecurityContextPropagationChannelInterceptor.postReceive()
where anAuthentication
can be propagated from the producer side.Also: the migration to the
AuthorizationChannelInterceptor
and its infrastructure we will have a long time ago requested SpEL support for security: https://jira.spring.io/projects/INT/issues/INT-1479The text was updated successfully, but these errors were encountered: