-
Notifications
You must be signed in to change notification settings - Fork 124
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
Integrate ca certificate flow #2462
Conversation
b2d4497
to
26cf81e
Compare
8ffc18e
to
a71fab3
Compare
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.
LGTM
54d0c93
to
3d446df
Compare
a71fab3
to
a9f650a
Compare
3d446df
to
ba79c6f
Compare
a9f650a
to
e39e656
Compare
ba79c6f
to
5fabe9a
Compare
e39e656
to
88b07eb
Compare
And the authenticator status check succeeds | ||
|
||
@skip | ||
# ONYX-15318 and ONYX-15317 are order sensitive tests |
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.
Seems like a bug not?
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.
Not. It's a proper work of cache.
If conjur already fetched keys from some url, keys remains in memory. So even there's no connectivity to jwks endpoint or like in example, I've added ca-cert variable with wrong cert chain; keys are already in memory - conjur does not invoke a request to bring them...
@@ -6,6 +6,17 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0. | |||
|
|||
## [Unreleased] | |||
|
|||
### Added | |||
- Added an ability to fetch signing keys from JWKS endpoints are using self-signed |
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.
Lists should be surrounded by blank lines
9efd5e8
to
fe2cc7f
Compare
The ca-cert value contains the X.509 public key certificate or certificate bundle. Each certificate in the bundle should be in PEM (RFC7468) format. The certificate(s) from the variable is/are replacing default operating system CA certificates bundle during fetching JWK Set from remote URI. Use the variable in order to establish TLS connection and validate server identity when the server is using self-signed certificate or certificate is signed by 3rd party CA.
fe2cc7f
to
6509507
Compare
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.
LGTM
Code Climate has analyzed commit 6509507 and detected 1 issue on this pull request. Here's the issue category breakdown:
The test coverage on the diff in this pull request is 100.0% (50% is the threshold). This pull request will bring the total coverage in the repository to 91.2% (0.1% change). View more on Code Climate. |
Desired Outcome
Enable JWT Authenticator to work with new
ca-cert
variable.Implemented Changes
CreateSigningKeyProvider
class passescert_store
parameter intoFetchJwksUriSigningKey
instanceConnected Issue/Story
ONYX-15872
Definition of Done
Changelog
CHANGELOG update
Test coverage
changes, or
Documentation
README
s) were updated in this PRBehavior
Security