kibana has no authentication
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla |
Fix Released
|
Critical
|
Alicja Kwasniewska | ||
Mitaka |
Fix Released
|
Critical
|
Alicja Kwasniewska |
Bug Description
Kibana has no authentication. One easy solution to fix this is to serve Kibana via Apache. Then the standard apache basic authentication methods can be used. Further Kibana can be made to use TLS authentication, as is currently done with Apache.
Then we can revert #1554977. #1554977 is a bit insecure because it requires giving access to the management network anyone that may want to look at the Kibana logs. Ideally the Kibana service would only be on the external network.
An example Apache authentication:
Listen 5601
<VirtualHost *:5601>
ServerName localhost
DocumentRoot /usr/share/kibana
<Directory /usr/share/kibana>
AuthType Basic
AuthName "Access Restricted"
AuthBasicPr
AuthUserFile /etc/httpd/
Require valid-user
</Directory>
Changed in kolla: | |
milestone: | mitaka-rc1 → mitaka-rc2 |
tags: | added: rc-backport-potential |
Changed in kolla: | |
milestone: | mitaka-rc2 → newton-1 |
tags: | removed: rc-backport-potential |
Changing to critical and assigning to our kibana expert because this is a security defect.
Regards
-steve