Public bug reported:
With notification enabled, a notification was not created but
The IP address in the notification was always the VIPip but not client ip if
sending request via VIP endpoint to keystones
For example:
Client IP: 192.168.245.2
VIP IP: 192.168.245.3
>From Client make a request
NO event notification was created.
This may cause a security issue.
** Affects: keystone
Importance: Undecided
Assignee: Thomas Hsiao (thomas-hsiao)
Status: New
** Changed in: keystone
Assignee: (unassigned) => Thomas Hsiao (thomas-hsiao)
--
You received this bug notif
, "user_allow_create": "False",
"tls_req_cert": "demand"...}}}
Once the config options created in the database, the user can even use
this invalid domain id to get/update/delete the config options, an
example as shown below:
~$ curl -k -H "X-Auth-Token:ADMIN"
http://localhost:353
2
is not supported for domain specific configurations", "code": 404, "title":
"Not Found"}}
** Affects: keystone
Importance: Undecided
Assignee: Thomas Hsiao (thomas-hsiao)
Status: New
** Changed in: keystone
Assignee: (unassigned) =>
4 matches
Mail list logo