[JBoss JIRA] (WFLY-11769) The wrong SecurityIdentity may be used for EE concurrency threads that are reused
by James Perkins (Jira)
James Perkins created WFLY-11769:
------------------------------------
Summary: The wrong SecurityIdentity may be used for EE concurrency threads that are reused
Key: WFLY-11769
URL: https://issues.jboss.org/browse/WFLY-11769
Project: WildFly
Issue Type: Bug
Components: Concurrency Utilities, Security
Reporter: James Perkins
Assignee: Eduardo Martins
The {{ElytronManagedThread}} stores a {{SecurityIdentity}} to run the thread as. These threads do not necessarily terminate if the keep alive time has not expired. This could cause a shared thread to use the wrong security identity when executing. This should likely be handled in a {{SetupContextHandle}}, however we need to examine the performance impact of this.
Using the {{SetupContextHandle}} would be the preferred method as it would need to execute after some of the other context handles so the correct TCCL would be seen for the {{SecurityDomain.getCurrent()}}.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months
[JBoss JIRA] (SWSQE-534) Kiali Test Mesh Operator
by Matt Mahoney (Jira)
[ https://issues.jboss.org/browse/SWSQE-534?page=com.atlassian.jira.plugin.... ]
Matt Mahoney updated SWSQE-534:
-------------------------------
Sprint: Kiali Sprint #16, Kiali Sprint #17, Kiali Sprint #19 (was: Kiali Sprint #16, Kiali Sprint #17, DUP Kiali Sprint #18)
> Kiali Test Mesh Operator
> ------------------------
>
> Key: SWSQE-534
> URL: https://issues.jboss.org/browse/SWSQE-534
> Project: Kiali QE
> Issue Type: QE Task
> Reporter: Matt Mahoney
> Assignee: Guilherme Baufaker Rêgo
> Priority: Minor
>
> Today, we do have some common situations concerning the meshes that we use to test istio and kiali
> 1) The version of Istio upstream installed on a cluster is different from istioctl which is installed on Jenkins slave which leads to a failure on the pipeline
> 2) Maistra doesn't provide an 'istioctl' and might be incompatible with upstream isctioctl command.
> 4) Maistra supported way to injection of the sidecar is the automatic injection and the present pipeline doesn't have this support
> 3) We are going to move to Central CI Jenkins on future so it might be complicated to configure the slaves specific.
> Since the new way to deploy cloud native applications on Kubernetes is the operators (https://github.com/operator-framework/operator-sdk) which encapsulate everything on the operator container (including the ansible flavor), it will simplify the pipeline.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 2 months