fix: remove unused Insecure field incorrectly assigned KeycloackEnabl…#452
Conversation
Priyanshubhartistm
requested review from
Harsh4902,
lbroudoux and
yada
as code owners
…e value The Insecure field in microcksClient was being assigned from configCtx.Server.KeycloackEnable (a Keycloak auth flag) which is semantically unrelated to TLS insecurity. Since the Insecure field was never read anywhere in the codebase after assignment, it was effectively dead code. This commit removes both the unused Insecure field from the microcksClient struct and its incorrect assignment in NewClient. The InsecureTLS field already correctly handles TLS skip-verify behavior via configCtx.Server.InsecureTLS. Fixes microcks#434 Signed-off-by: Priyanshubhartistm <bhartipriyanshustm@gmail.com>
Priyanshubhartistm
force-pushed
the
fix/remove-insecure-field-incorrect-assignment
branch
from
d799248 to
2229042
Compare
|
This pull request has been automatically marked as stale because it has not had recent activity 😴 It will be closed in 30 days if no further activity occurs. To unstale this pull request, add a comment with detailed explanation. There can be many reasons why some specific pull request has no activity. The most probable cause is lack of time, not lack of interest. Microcks is a Cloud Native Computing Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model. Let us figure out together how to push this pull request forward. Connect with us through one of many communication channels we established here. Thank you for your patience ❤️ |
|
Hii @lbroudoux , @Harsh4902 could you please take a look at this PR? whenever you have sometime, I would really appreciate your review and any feedback or suggestions you may have. Thank you |
1 participant
Description
pkg/connectors/microcks_client.go, theNewClientfunction incorrectly assignedconfigCtx.Server.KeycloakEnable(a boolean flag for Keycloak authentication) to thec.Insecurefield (which semantically represents TLS insecurity). This meant that when Keycloak was enabled,c.Insecurewas set totrue- a completely unrelated concern.Insecurefield from themicrocksClientstruct and its incorrect assignment (c.Insecure = configCtx.Server.KeycloakEnable) inNewClient.Insecurefield was never read anywhere in the codebase after being assigned, making it dead code. TheInsecureTLSfield already correctly handles TLS skip-verify behavior viaconfigCtx.Server.InsecureTLS, so no functionality is lost.Related issue(s)
Fixes #434