-
Notifications
You must be signed in to change notification settings - Fork 14
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
Errors are unnecessarily logged on client prior to certificate being injected #119
Comments
Hi @eranha, With that pre-requisite as a starting point, we do not have too many reliable options available to us from the authenticator. Are you suggesting that we use a different type of checks? If so, there is room for improvement here for sure but as-is described, this behavior is not exactly a bug. Let us know what you wanted to specifically to see here and we can try to refine the issue. |
The error is logged because the certificate has not been injected yet. You can wait/retry for it, and only log an error after timeout |
Hi @eranha, |
See more detail here: #146 |
### Fixed - Logs now correctly print only the Conjur identity without the policy branch prefix. ([#126](#126)) - When authentication fails, the exponential backoff retry is correctly reset so that it will continue to attempt to authenticate until backoff is exhausted. ([#158](#158)) ### Changed - Wait slightly for the client certificate file to exist after login before raising an error. [#119](#119)
### Fixed - Logs now correctly print only the Conjur identity without the policy branch prefix. ([#126](#126)) - When authentication fails, the exponential backoff retry is correctly reset so that it will continue to attempt to authenticate until backoff is exhausted. ([#158](#158)) ### Changed - Wait slightly for the client certificate file to exist after login before raising an error. [#119](#119)
### Fixed - Logs now correctly print only the Conjur identity without the policy branch prefix. ([#126](#126)) - When authentication fails, the exponential backoff retry is correctly reset so that it will continue to attempt to authenticate until backoff is exhausted. ([#158](#158)) ### Changed - Wait slightly for the client certificate file to exist after login before raising an error. [#119](#119)
This version introduces some changes that we can benefit from, especially these: - Errors in the certificate injection process on login are now printed to the client logs. [cyberark/conjur-authn-k8s-client#/170](cyberark/conjur-authn-k8s-client#170) - When authentication fails, the exponential backoff retry is correctly reset so that it will continue to attempt to authenticate until backoff is exhausted. [cyberark/conjur-authn-k8s-client#158](cyberark/conjur-authn-k8s-client#158) - Wait slightly for the client certificate file to exist after login before raising an error. [cyberark/conjur-authn-k8s-client#119](cyberark/conjur-authn-k8s-client#119)
This version introduces some changes that we can benefit from, especially these: - Errors in the certificate injection process on login are now printed to the client logs. [cyberark/conjur-authn-k8s-client#/170](cyberark/conjur-authn-k8s-client#170) - When authentication fails, the exponential backoff retry is correctly reset so that it will continue to attempt to authenticate until backoff is exhausted. [cyberark/conjur-authn-k8s-client#158](cyberark/conjur-authn-k8s-client#158) - Wait slightly for the client certificate file to exist after login before raising an error. [cyberark/conjur-authn-k8s-client#119](cyberark/conjur-authn-k8s-client#119)
This version introduces some changes that we can benefit from, especially these: - Errors in the certificate injection process on login are now printed to the client logs. [cyberark/conjur-authn-k8s-client#/170](cyberark/conjur-authn-k8s-client#170) - When authentication fails, the exponential backoff retry is correctly reset so that it will continue to attempt to authenticate until backoff is exhausted. [cyberark/conjur-authn-k8s-client#158](cyberark/conjur-authn-k8s-client#158) - Wait slightly for the client certificate file to exist after login before raising an error. [cyberark/conjur-authn-k8s-client#119](cyberark/conjur-authn-k8s-client#119)
This version introduces some changes that we can benefit from, especially these: - Errors in the certificate injection process on login are now printed to the client logs. [cyberark/conjur-authn-k8s-client#/170](cyberark/conjur-authn-k8s-client#170) - When authentication fails, the exponential backoff retry is correctly reset so that it will continue to attempt to authenticate until backoff is exhausted. [cyberark/conjur-authn-k8s-client#158](cyberark/conjur-authn-k8s-client#158) - Wait slightly for the client certificate file to exist after login before raising an error. [cyberark/conjur-authn-k8s-client#119](cyberark/conjur-authn-k8s-client#119)
This version introduces some changes that we can benefit from, especially these: - Errors in the certificate injection process on login are now printed to the client logs. [cyberark/conjur-authn-k8s-client#/170](cyberark/conjur-authn-k8s-client#170) - When authentication fails, the exponential backoff retry is correctly reset so that it will continue to attempt to authenticate until backoff is exhausted. [cyberark/conjur-authn-k8s-client#158](cyberark/conjur-authn-k8s-client#158) - Wait slightly for the client certificate file to exist after login before raising an error. [cyberark/conjur-authn-k8s-client#119](cyberark/conjur-authn-k8s-client#119)
This version introduces some changes that we can benefit from, especially these: - Errors in the certificate injection process on login are now printed to the client logs. [cyberark/conjur-authn-k8s-client#/170](cyberark/conjur-authn-k8s-client#170) - When authentication fails, the exponential backoff retry is correctly reset so that it will continue to attempt to authenticate until backoff is exhausted. [cyberark/conjur-authn-k8s-client#158](cyberark/conjur-authn-k8s-client#158) - Wait slightly for the client certificate file to exist after login before raising an error. [cyberark/conjur-authn-k8s-client#119](cyberark/conjur-authn-k8s-client#119)
Afte the CSR is sent the server and the response is being sent out-of-band, the client yields errors to log while attempting to load the certificate, until the server injects the certificate to the client. This type of output can be alarming to see and unhelpful so it would be good to only show this when there is a real problem getting the certificate.
AC:
The text was updated successfully, but these errors were encountered: