Hi Arif--
Are you using Keystone for authentication?
If so, you need to get an authentication token from Keystone and add it as a header to your curl command: -H "X-Auth-Token:$TOKEN".
You do not need to specify the project ID (-H 'X-Project-Id:12345'). The project ID will be based on your Keystone user's project ID.
--Dave
From: OpenStack Mailing List Archive <corpqa at gmail.com<mailto:corpqa at gmail.com>>
Reply-To: "openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Wednesday, October 21, 2015 at 3:11 AM
To: "openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: [openstack-dev] openstack-barbican-authenticate-keystone-barbican-command
Link: https://openstack.nimeyo.com/62868/?show=62868#q62868
From: marif82 <marif82 at gmail.com<mailto:marif82 at gmail.com>>
Hi Asha,
I am also getting the same error when I am executing the curl command to create secret.
bash-4.2$ curl -X POST -H 'content-type:application/json' -H 'X-Project-Id:12345' -d '{"payload": "my-secret-here","payloadcontenttype": "text/plain"}' http://localhost:9311/v1/secrets
Authentication requiredbash-4.2$
Can you please help me how you have solved this problem. I am using the safenet HSM for MKEK and HMAC and it generated successfully on HSM partition.
Please help me to resolve this issue.
Thanks & Regards,
Arif
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/0784a1ed/attachment.html>