I'm not sure what you're expecting here? You intentionally put garbage
data into keystone's configuration and it's appropriately reporting an
error against that data. You can bypass the authentication process by
using keystone.conf [DEFAULT] admin_token instead of trying to use
credentials and consuming the catalog, and use endpoint-list / endpoint-
delete appropriately.
** Changed in: keystone
Status: New => Won't Fix
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1272158
Title:
endpoint creation failed with special char
Status in OpenStack Identity (Keystone):
Won't Fix
Bug description:
1. I wrote tempest to run against keystone endpoint-create "'!@#$%^*')" in
url，
2. After I create, I can not run keystone endpoint-list to get the
endpoint,but keystone can not run any more.
[root@localhost ~]# keystone endpoint-list
Authorization Failed: KS-7406845 Malformed endpoint URL
(url!@#$%^*-tempest-952498848), see ERROR log for details. (HTTP 500
3. So I think there is a error there, we can not deal with special char.
4. After I rerun installation on keystone,glance, the problem did not
existed.So I think these special char disturb the keystone database.
To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1272158/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
