Hi, A token issue is done with a POST request not a GET request, so the request should be:
curl -X POST ... and Keystone requires perhaps Accept header. Cédric/ZZelle On Mon, Jul 25, 2016 at 3:19 AM, Kenny Ji-work <[email protected]> wrote: > Hi all, > > In the mitaka version, I used v2 RESTful API of keystone as following: > curl -i -H "Content-Type: application/json" -d ' > { "auth": { > "tenantName": "admin", > "passwordCredentials": { > "username": "admin", > "password": "password" > } > } > }' http://10.240.227.7:35357/v2.0/tokens ; echo > > But the result shows: {"error": {"message": "The request you have made > requires authentication.", "code": 401, "title": "Unauthorized"}}. But the > v3 of keystone works normaly. > Is v2 of keystone not supported in mitaka or something else config I > config wrong? > > Sincerely! > Kenny Ji > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
