KNOX-3105 - Add Topology Level Config for Truststore to RemoteAuthProvider #1001
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?
I originally had this topology level config only for the truststore and password but decided that it should be configured at the gateway level. However, it is much easier to use specific truststores for dev and testing environments than adding a cert from one Knox to another's truststore which may have other certs, etc.
This change will add the params for location and password with alias service support of the password.
How was this patch tested?
Added new unit tests, ran all existing tests and manually tested with another knox instance.
curl -ivku admin:admin-password https://localhost:8444/gateway/tokengen/knoxtoken/api/v1/token
Audit logs for each instance are below to show the correlation ID across instances:
Local instance:
remote instance:
The local instance above is running on port 8444 and the remote instance on 8443.