-
Notifications
You must be signed in to change notification settings - Fork 24.9k
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
[CI] FIPS FollowIndexIT testDowngradeRemoteClusterToBasic failure to recreate SSL context #52034
Labels
:Security/Security
Security issues without another label
Team:Security
Meta label for security team
>test-failure
Triaged test failures from CI
Comments
albertzaharovits
added
>test-failure
Triaged test failures from CI
:Distributed Indexing/CCR
Issues around the Cross Cluster State Replication features
labels
Feb 7, 2020
Pinging @elastic/es-distributed (:Distributed/CCR) |
albertzaharovits
changed the title
FollowIndexIT testDowngradeRemoteClusterToBasic failure to recreate SSL context
[CI] FollowIndexIT testDowngradeRemoteClusterToBasic failure to recreate SSL context
Feb 7, 2020
Ooops, I just realized the name of the job |
albertzaharovits
added
:Security/Security
Security issues without another label
and removed
:Distributed Indexing/CCR
Issues around the Cross Cluster State Replication features
labels
Feb 7, 2020
Pinging @elastic/es-security (:Security/Security) |
cc @jkakavas |
albertzaharovits
changed the title
[CI] FollowIndexIT testDowngradeRemoteClusterToBasic failure to recreate SSL context
[CI] FIPS FollowIndexIT testDowngradeRemoteClusterToBasic failure to recreate SSL context
Feb 7, 2020
jkakavas
added a commit
to jkakavas/elasticsearch
that referenced
this issue
Feb 7, 2020
Our FIPS 140 testing depends on setting the appropriate java policy in order to configure the JVM in FIPS mode. Some tests ( discovery-ec2 and ccr qa ) also needed to set a custom policy file to grant a specific permission, which overwrote the FIPS related policy and tests would fail. This change ensures that when a custom policy needs to be set in these tests, the permissions that are necessary for FIPS are also set. Resolves: elastic#51685, elastic#52034
jkakavas
added a commit
that referenced
this issue
Feb 8, 2020
Our FIPS 140 testing depends on setting the appropriate java policy in order to configure the JVM in FIPS mode. Some tests ( discovery-ec2 and ccr qa ) also needed to set a custom policy file to grant a specific permission, which overwrote the FIPS related policy and tests would fail. This change ensures that when a custom policy needs to be set in these tests, the permissions that are necessary for FIPS are also set. Resolves: #51685, #52034
jkakavas
added a commit
to jkakavas/elasticsearch
that referenced
this issue
May 21, 2020
Our FIPS 140 testing depends on setting the appropriate java policy in order to configure the JVM in FIPS mode. Some tests ( discovery-ec2 and ccr qa ) also needed to set a custom policy file to grant a specific permission, which overwrote the FIPS related policy and tests would fail. This change ensures that when a custom policy needs to be set in these tests, the permissions that are necessary for FIPS are also set. Resolves: elastic#51685, elastic#52034
jkakavas
added a commit
that referenced
this issue
May 21, 2020
Our FIPS 140 testing depends on setting the appropriate java policy in order to configure the JVM in FIPS mode. Some tests ( discovery-ec2 and ccr qa ) also needed to set a custom policy file to grant a specific permission, which overwrote the FIPS related policy and tests would fail. This change ensures that when a custom policy needs to be set in these tests, the permissions that are necessary for FIPS are also set. Resolves: #51685, #52034
Resolved in #52046 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
:Security/Security
Security issues without another label
Team:Security
Meta label for security team
>test-failure
Triaged test failures from CI
This reproduces on master!
Build scans:
https://gradle-enterprise.elastic.co/s/wfh66uffpg4hy
https://gradle-enterprise.elastic.co/s/ppmoxjtf2cvby
https://gradle-enterprise.elastic.co/s/b6kyaeu7kqrfy
The text was updated successfully, but these errors were encountered: