This question has been raised in the Kibana community already:
IMHO, it affects Elasticsearch and Shield as well.
Does Shield provide an interface where I can handle the authentication process (validate SAML token) and then provide Shield the roles the user has by parsing the attributes in the SAML token.
Thanks for the feedback. Can you shed some light on it which industry standards you plan to follow? Do you also have a rough timeline like Q3, Q4, next year?
These are great questions! We have plans to add support for a number of new auth realms. In the very near future, we are planning to add a PKI-based realm that will make application-level authentication using certificates much easier.
In the longer term - think within this calendar year - we are planning to add additional realms and also allow the realms system to be extended. With the extensibility, it would be straightforward to create your own custom realm for your SAML-based SSO system.
Given the widespread adoption of SAML authentication/authorization in public clouds it may be prudent to include an example implementation of SAML via a custom auth realm using any SAML IdP as a point of reference to provide your customers with a working example which can be modified (if necessary) to work with their own IdP's. One of your competitors recently released native SAML v2.0 SSO/SLO support using the following IdP:
There are many organizations that required this type of functionality from production systems hosted in public clouds which could be a barrier to adoption for your project.
I also agree that this needs to be implemented in Shield, simply implementing in Kibana is a half baked solution that isn't going to satisfy security requirements at many organizations.
It doesn't do any good to use SAML for SSO/SLO if you still have to make an LDAP endpoint available for authorization so using authentication proxies for this doesn't really solve the problem at hand.
We would love to have SAML support natively in shield. Through our idp (OneLogin) we provide 2fa as well as a bunch of other ip related restrictions so it would be nice if we could apply these same practices with kibana.
I'm the product manager focusing on x-pack security. We have working happening to support SAML right now. When exactly it will land isn't known yet (there's still a lot of work to do), but it should be supported in the near future. This is literally my #1 feature.
Feel free to let me know if you have any questions.
Apologies for being picky, but this is a major hurdle for the company I work for to adopt X-Pack. Do you think it will be available this year? knowing roughly when it could land would enable me to work around it and inform my stakeholders. If you could give a ball park period of half 2 this year, half 1 next year, end of next year etc I am sure many other enterprise companies would be content.
I can't give a great answer unfortunately, there are many moving parts to support this across the stack. The earliest we could maybe see a beta would be end of this calendar year. Feel free to message me near the end of summer, I may have a more concrete timeline by then.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.