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
This issue is a follow up from Spring Cloud Security issue #87. I came to the conclusion that the request feature was Hystrix focused rather than Spring Cloud Security. Spring Cloud Security is aimed towards OAuth2 support.
Hystrix commands are actually unable to access the security context if executed with an isolation strategy set to THREAD. Only workaround available consists in setup the execution isolation to SEMAPHORE.
Using Hystrix command hooks, we could build an infrastructure to transfert the Security Context from the main thread to the one executing the Hystrix command.
The text was updated successfully, but these errors were encountered:
daniellavoie
changed the title
Transfer security context from feign client to hystrix execution context
Expose security context of a feign client to an hystrix command.
May 29, 2016
daniellavoie
changed the title
Expose security context of a feign client to an hystrix command.
Expose security context to any Hystrix command.
Jun 10, 2016
This issue is a follow up from Spring Cloud Security issue #87. I came to the conclusion that the request feature was Hystrix focused rather than Spring Cloud Security. Spring Cloud Security is aimed towards OAuth2 support.
Hystrix commands are actually unable to access the security context if executed with an isolation strategy set to
THREAD
. Only workaround available consists in setup the execution isolation to SEMAPHORE.Using Hystrix command hooks, we could build an infrastructure to transfert the Security Context from the main thread to the one executing the Hystrix command.
The text was updated successfully, but these errors were encountered: