Closed amarrocco84 closed 4 years ago
@amarrocco84 I think we need more info on this - I cannot replicate the error here on a vanilla ubuntu VM:
$ export CONJUR_DATA_KEY="$(< data_key)"
...
$ sudo -E docker-compose up -d
...
$ sudo docker-compose exec conjur conjurctl account create myConjurAccount
...
$ sudo docker-compose exec client conjur init -u conjur -a myConjurAccount
...
$ sudo docker-compose exec client conjur policy load root policy/BotApp.yml
Enter your username to log into Conjur: admin
Please enter your password (it will not be echoed):
Loaded policy 'root'
{
"created_roles": {
"myConjurAccount:user:Dave@BotApp": {
"id": "myConjurAccount:user:Dave@BotApp",
"api_key": "p7c6a21ast8zdpp5p6jgg642a8xyemf2c7b32t1f24ev3jtc7zs"
},
"myConjurAccount:host:BotApp/myDemoApp": {
"id": "myConjurAccount:host:BotApp/myDemoApp",
"api_key": "27f4zct32a31dd2gajqn81eqq6ff1zycfe81n13ar42h0t4721qjbsqd"
}
},
"version": 1
}
I was able to get this to work in a fresh Unbuntu environment. Thank you for the help!
@amarrocco84 anytime :)
When I run this command "docker-compose exec client conjur policy load root policy/BotApp.yml > my_app_data" I get the following in the my_app_data.
"error: No such file or directory @ rb_sysopen - policy/BotApp.yml"