Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Can't run testEC2DiscoveryRetriesOnRateLimiting in FIPS 140 mode #51685

Closed
jkakavas opened this issue Jan 30, 2020 · 2 comments · Fixed by #52046
Closed

Can't run testEC2DiscoveryRetriesOnRateLimiting in FIPS 140 mode #51685

jkakavas opened this issue Jan 30, 2020 · 2 comments · Fixed by #52046
Labels
:Distributed Coordination/Discovery-Plugins Anything related to our integration plugins with EC2, GCP and Azure :Security/Security Security issues without another label >test-failure Triaged test failures from CI

Comments

@jkakavas
Copy link
Member

We define a custom java policy in plugins/discovery-ec2/build.gradle to give an extra permission, so we can't run this in FIPS mode as it needs its own specific policy file. We should look into merging these policies if possible. For now, I will mute the test in FIPS mode.
@jkakavas jkakavas added >test-failure Triaged test failures from CI :Distributed Coordination/Discovery-Plugins Anything related to our integration plugins with EC2, GCP and Azure :Security/Security Security issues without another label labels Jan 30, 2020
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-security (:Security/Security)

@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed (:Distributed/Discovery-Plugins)

jkakavas added a commit to jkakavas/elasticsearch that referenced this issue Jan 30, 2020
@jkakavas
Mute ec2 test in FIPS 140 mode
c62ebc6 
as it needs an extra permission, until we can figure out how to
grant the permission in FIPS 140 mode too.

See: elastic#51685
@jkakavas jkakavas mentioned this issue Jan 30, 2020
Merged
jkakavas added a commit that referenced this issue Jan 30, 2020
@jkakavas
Mute ec2 test in FIPS 140 mode (#51686)
a59095e 
as it needs an extra permission, until we can figure out how to
grant the permission in FIPS 140 mode too.

See: #51685
jkakavas added a commit to jkakavas/elasticsearch that referenced this issue Jan 31, 2020
@jkakavas
Mute ec2 test in FIPS 140 mode (elastic#51686)
efc5d66 
as it needs an extra permission, until we can figure out how to
grant the permission in FIPS 140 mode too.

See: elastic#51685
jkakavas added a commit to jkakavas/elasticsearch that referenced this issue Jan 31, 2020
@jkakavas
Mute ec2 test in FIPS 140 mode (elastic#51686)
1b1790b 
as it needs an extra permission, until we can figure out how to
grant the permission in FIPS 140 mode too.

See: elastic#51685
jkakavas added a commit to jkakavas/elasticsearch that referenced this issue Jan 31, 2020
@jkakavas
Mute ec2 test in FIPS 140 mode (elastic#51686)
d67aafe 
as it needs an extra permission, until we can figure out how to
grant the permission in FIPS 140 mode too.

See: elastic#51685
jkakavas added a commit to jkakavas/elasticsearch that referenced this issue Jan 31, 2020
@jkakavas
Mute ec2 test in FIPS 140 mode (elastic#51686)
d7fa8cd 
as it needs an extra permission, until we can figure out how to
grant the permission in FIPS 140 mode too.

See: elastic#51685
This was referenced Jan 31, 2020
Merged
Merged
jkakavas added a commit that referenced this issue Jan 31, 2020
@jkakavas
Mute ec2 test in FIPS 140 mode (#51686) (#51726)
1dc965f 
as it needs an extra permission, until we can figure out how to
grant the permission in FIPS 140 mode too.

See: #51685
jkakavas added a commit that referenced this issue Jan 31, 2020
@jkakavas
Mute ec2 test in FIPS 140 mode (#51686) (#51727)
598c378 
as it needs an extra permission, until we can figure out how to
grant the permission in FIPS 140 mode too.

See: #51685
jkakavas added a commit to jkakavas/elasticsearch that referenced this issue Feb 7, 2020
@jkakavas
Fix custom policy in plugins in FIPS 140
0b650cd 
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 jkakavas mentioned this issue Feb 7, 2020
Merged
jkakavas added a commit that referenced this issue Feb 8, 2020
@jkakavas
Fix custom policy in plugins in FIPS 140 (#52046)
043279a 
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
@jkakavas
Fix custom policy in plugins in FIPS 140 (elastic#52046)
a400d2f 
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
@jkakavas
Fix custom policy in plugins in FIPS 140 (#52046) (#57049)
6c90727 
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
:Distributed Coordination/Discovery-Plugins Anything related to our integration plugins with EC2, GCP and Azure :Security/Security Security issues without another label >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix custom policy in plugins in FIPS 140 jkakavas/elasticsearch
2 participants
@jkakavas @elasticmachine