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.

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

Merge "Avoid silencing ClassNotFoundException in FIPS mode" to 0.43 #719

Merged
merged 2 commits into from
Dec 4, 2023

Conversation

pshipton
Copy link
Member

@pshipton pshipton commented Dec 4, 2023

No description provided.

KostasTsiounis and others added 2 commits December 4, 2023 13:56
When checking whether available services exist, if RestrictedSecurity is
enabled, the class has to be loaded to check whether it extends the
java.security.Provider class.

If the class cannot be found, a ClassNotFoundException is thrown and
caught without taking further action. That, however, goes against the
expected behaviour. The service must appear as available, and only
attempting to load should trigger a ClassNotFoundException, which will
be transformed into a ServiceConfigurationError.

This change tries to load the next service to check if it should be
allowed based on RestrictedSecurity criteria. If that succeeds, the
loaded class is saved to be used when trying to get it in
nextService(). Otherwise, a boolean variable is set to signify an
exception should be thrown. The process continues until an appropriate
service is found or one is responsible for a ClassNotFoundException.

Signed-off-by: Kostas Tsiounis <kostas.tsiounis@ibm.com>
Avoid silencing ClassNotFoundException in FIPS mode
@JasonFengJ9 JasonFengJ9 merged commit fa19bfd into v0.43.0-release Dec 4, 2023
9 of 27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants