Spring Security SEC-1539: More flexible run-as authentication and security context propagation support

Luke Taylor (Migrated from SEC-1539) said:

It should be possible to set up infrastructure for running a service (or service method) with a particular SecurityContext. This could be done either to satisfy internal security constraints within the application or to allow the propagation of credentials for invoking a remote service (e.g. s3), which would also require protocol-specific integration. This would thus be a superset of the existing run-as functionality which would be superseded and removed from the security interceptor. It would also supersede functionality like the WebSphere2SpringSecurityPropagationInterceptor.

Comment From: rwinch

This can be done using DelegatingSecurityContextRunnable