Update README.md - OIDC with self-signed certificates guidance #242
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.
…OIDC
Artifactory uses the GitHub Actions' built-in HTTP client to download the JFrog CLI and perform authentication with JFrog Access for OpenID Connect (OIDC).
When an Artifactory instance is using self-signed certificates, you may run into the following error when exchanging token with OIDC:
Error: Exchanging JSON web token with an access token failed: self-signed certificate in certificate chain
This error occur can occur when trying to exchange a token for OIDC.
To resolve this we need to add the certificates to the NODE_EXTRA_CA_CERTS environmental variable.
Added a section explaining the use of self-signed certificates with OIDC/Github actions.
Provided guidance on how to configure self-signed certificates in the context of OIDC.
All tests passed. If this feature is not already covered by the tests, I added new tests.
I used
npm run format
for formatting the code before submitting the pull request.