KNOX-1801 - Master secret is incorrectly assumed when a custom truststore is not specified when clientauth is enabled #63
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Master secret is incorrectly assumed when a custom truststore is not specified when clientauth is enabled.
Steps to reproduce
gateway-site.xml
gateway.tls.keystore.password.alias
gateway.tls.keystore.path
gateway.tls.keystore.type
gateway.tls.key.alias
gateway.tls.key.passphrase.alias
(optional)gateway.client.auth.needed
: {{true}}bin/knoxcli.sh create-alias gateway-identity-keystore-password --value <password>
The Gateway will fail to start with the following error in the gateway.log:
Solution
Lookup password for the truststore using the appropriate alias name, falling back to the master secret if an alias is not configured or not set.
While at it, cleaned up
org.apache.knox.gateway.services.security.impl.JettySSLService
to remove unneededMasterService
calls.How was this patch tested?
Added new unit tests -
org.apache.knox.gateway.services.security.impl.JettySSLServiceTest
Manually tested various scenarios.
Please review Knox Contributing Process before opening a pull request.