-
Notifications
You must be signed in to change notification settings - Fork 604
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
refactoring ProtocolHelper #30657
base: integration
Are you sure you want to change the base?
refactoring ProtocolHelper #30657
Conversation
Looking at the code before, it doesn't make sense to me that we handled single item lists differently than lists with multiple items. It seems the previous code would use a cache only if multi-protocol is specified. That would cause performance slowdown on single-protocol lists since it would execute This change uses a cache for any sized list. It simplifies the loop which validates the protocol by using the same loop regardless of FIPS being enabled or not Lastly, we could simplify this even farther by checking the cache before we check allowedProtocols. I didn't make this change because it would break in the case that the user enabled fips without restarting their server.
to
|
5b5666b
to
133d49c
Compare
#build (view Open Liberty Personal Build - ❌ completed with errors/failures.) Note: Target locations of links might be accessible only to IBM employees. |
Code analysis and actionsDO NOT DELETE THIS COMMENT.
|
Your personal build request is at https://wasrtc.hursley.ibm.com:9443/jazz/resource/itemOid/com.ibm.team.build.BuildResult/_SDtiwN4MEe-M5OZShUU9WA Target locations of links might be accessible only to IBM employees. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a slight behavior change that could break customers. In the protocol length of 1 scenario, we allowed any protocol even if it wasn't in the MULTI_PROTOCOL_LIST
list. It appears that in the > 1 scenario we care about the list not containing certain protocols. To not break existing customers, I believe we would have to have logic for 140-3 to check the FIPS_140_3_PROTOCOLS
whether providing 1 or more than 1 protocol, but for the 1 protocol, we wouldn't do a check against allowedProtocols if not using 140-3.
#build (view Open Liberty Personal Build - ❌ completed with errors/failures.) Note: Target locations of links might be accessible only to IBM employees. |
Code analysis and actionsDO NOT DELETE THIS COMMENT.
|
Your personal build request is at https://wasrtc.hursley.ibm.com:9443/jazz/resource/itemOid/com.ibm.team.build.BuildResult/_Oa2ykd8FEe-M5OZShUU9WA Target locations of links might be accessible only to IBM employees. |
Resolves #30583