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

(fips) Remove kerberos as an option in FIPS mode #42867

Open
simitt opened this issue Feb 24, 2025 · 4 comments
Open

(fips) Remove kerberos as an option in FIPS mode #42867

simitt opened this issue Feb 24, 2025 · 4 comments
Assignees
@kruskall
Labels
needs_team Indicates that the issue/PR needs a Team:* label

Comments

@simitt
Copy link
Contributor

simitt commented Feb 24, 2025 •
edited
Loading

When running a beat in FIPS mode, Kerberos needs to be disabled for any beat in FIPS mode. No kerberos.* configuration options should be exposed in the reference and yaml file for the FIPS compliant beats. Any configured kerberos settings need to be ignored and kerberos clients can not be instantiated in FIPS mode.
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Feb 24, 2025
@botelastic
Copy link

botelastic bot commented Feb 24, 2025

This issue doesn't have a Team:<team> label.

This was referenced Feb 24, 2025
Merged
Open
Open
Open
Open
@simitt
Copy link
Contributor Author

simitt commented Feb 24, 2025

elastic/sarama#22 as tackling part of this card

This was referenced Feb 25, 2025
Open
Open
Open
@jlind23
Copy link
Collaborator

jlind23 commented Feb 25, 2025

@kruskall this comment means that you will tackle all other sub issues here right? If yes, I'm happy to assign this issue to you.

@kruskall
Copy link
Member

kruskall commented Feb 25, 2025 •
edited
Loading

Yes, this (and all other subissues) should be fixed by #42887

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kruskall kruskall

Labels
needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@simitt @jlind23 @kruskall