You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So we've been using Conjur-OSS for some time now, primarily to help with rotating AWS credentials, which has worked fine previously. But recently we noticed that the rotations has failed silently, and has done so for quite a long time, with no log messages that we could find as to why.
So I'm wondering, should there be logs printed about the rotator failure? Do we need to tweak the log-level (didn't find if that was possible with OSS, though the Enterprise version said you could set a environment variable for it)?
Steps to Reproduce
Haven't tested it on a "clean" instance, but whenever we create a new set of variables (all according to docs) and initialize them with the AWS credentials (and the User has correct IAM permissions), they don't rotate. Existing variables that have been able to rotate previously, have also stopped.
Summary
So we've been using Conjur-OSS for some time now, primarily to help with rotating AWS credentials, which has worked fine previously. But recently we noticed that the rotations has failed silently, and has done so for quite a long time, with no log messages that we could find as to why.
So I'm wondering, should there be logs printed about the rotator failure? Do we need to tweak the log-level (didn't find if that was possible with OSS, though the Enterprise version said you could set a environment variable for it)?
Steps to Reproduce
Haven't tested it on a "clean" instance, but whenever we create a new set of variables (all according to docs) and initialize them with the AWS credentials (and the User has correct IAM permissions), they don't rotate. Existing variables that have been able to rotate previously, have also stopped.
Expected Results
Actual Results
Credentials are not rotated and no logs appear.
Reproducible
Always the same result for us, but haven't tested on a "clean" setup.
Version/Tag number
We're running rather old versions of the docker images (planning to update soon),
Docker Engine Client/Server - 19.03.13
Environment setup
The text was updated successfully, but these errors were encountered: