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

Adding test coverage to support encrypted PEM Keys #1508

Closed
wants to merge 1 commit into from
Closed

Adding test coverage to support encrypted PEM Keys #1508

wants to merge 1 commit into from
+160 −0

Conversation

jcarranzan
Copy link
Contributor

@jcarranzan jcarranzan commented Feb 26, 2025 •
edited
Loading

Summary

These tests will be added to cover 44549 :

  • Https communication using encrypted Pem, ensure you can communicate with Quarkus REST endpoint using HTTPS (no client-side authentication).
  • Certificate reloading, validate with newly generated certificate, it works for encrypted PEMs as well .
  • Injecting TLS registry configuration and can see the private key decrypted (so you can see keystore and check some x509 attributes).

Please check the relevant options

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Dependency update
  • Refactoring
  • Release (follows conventions described in the RELEASE.md)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • This change requires a documentation update
  • This change requires execution against OCP (use run tests phrase in comment)

Checklist:

  • [x ] Example scenarios has been updated / added
  • Methods and classes used in PR scenarios are meaningful
  • Commits are well encapsulated and follow the best practices

@jcarranzan
Adding test coverage to support encrypted PEM Keys
816fd16 
These tests will be added:
- Https communication using encrypted Pem,  ensure you can communicate with Quarkus REST endpoint using HTTPS (no client-side authentication).
- Certificate reloading, validate with newly generated certificate, it works for encrypted PEMs as well .
- Injecting TLS registry configuration and can see the private key decrypted (so you can see keystore and check some x509 attributes).
- FIPS compatibility, it works under FIPS enable environment.
@jcarranzan jcarranzan force-pushed the tests-encrypted-PEM-certificates branch from c041838 to 816fd16 Compare February 26, 2025 15:01
@jcarranzan
Copy link
Contributor Author

I will close this PR to move these tests to the TS in another PR

@jcarranzan jcarranzan closed this Feb 27, 2025
@jcarranzan jcarranzan mentioned this pull request Feb 27, 2025
Open
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@michalvavrik michalvavrik Awaiting requested review from michalvavrik

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@jcarranzan