-
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
No default behavior for CONJUR_VERSION parameter #70
No default behavior for CONJUR_VERSION parameter #70
Comments
Thanks for adding this issue @JfcAtCyberArk - I 100% agree and generally think most of our integrations should have this behavior (default to 5, but allow specifying 4 if using an older version of Conjur Enterprise v4.x) To be totally clear, I'll see what we can do about getting a fix for this into our queue to address soon. |
Note: AC for making this update:
|
These changes are available in v0.16.1 (I actually think this functionality was available as early as v0.13.0), but we'll aim to propagate them to the downstream projects with PRs now (cc @BradleyBoutcher) |
…nt#70-bump-authn-k8s-client-version Bump authn-k8s client to v0.16.1
Hi @izgeri @BradleyBoutcher, What I meant by a "Default Behavior" was that any other value than '4' would use '5' behind the scenes but it is not the case. I just ran into an issue because my authenticator was failing when I provided it CONJUR_VERSION=11.4.0 and I had to come back to the source code to understand why. I feel like I did not explain enough what I meant by a default behavior, sorry for that. Please let me know! JFC |
I also think dockerhub doc is not really clear. |
@JfcAtCyberArk all of our clients and tools expect the value to be either 4 or 5, and no other value. At current, the authn-k8s client defaults to 5 if no value is specified, and errors if the value is not 4 or 5. I've updated both DockerHub pages for this project to list Hope this makes sense, but please feel free to weigh in if you have any other suggestions. |
@izgeri It totally makes sense! JFC |
@JfcAtCyberArk you will be glad to hear we are trying to default this to 5 everywhere possible, and to remove it from the DAP / Conjur OSS documentation once we do. If there is a project where this is especially valuable for you and you don't see an existing gh issue for that change, please file one and let us know so we can update it soon! |
Hi there,
There is no default behavior if the CONJUR_VERSION is not set, or not 4 or 5.
Code reference:
https://github.com/cyberark/conjur-authn-k8s-client/blob/master/pkg/authenticator/authenticator.go#L230
In that case, the authenticator fails with the following entry in the logs:
CAKC011I Login request to:
It's really not intuitive.
Actual version of DAP is 11.2.1 - to be aligned with CyberArk suite, version 4 is really far now.
I think a default behavior would make sense.
Following DockerHub links may also be required an update:
https://hub.docker.com/r/cyberark/conjur-kubernetes-authenticator/
https://hub.docker.com/r/cyberark/conjur-authn-k8s-client
Many thanks!
JFC
The text was updated successfully, but these errors were encountered: