[Kolab-devel] [3.5] Installation on CentOS: webadmin login

Jochen Hein jochen at jochen.org
Sat Jan 23 23:15:34 CET 2016


Hello,

I've tried another installation of Kolab Development, this time on
CentOS 7.2.  After installation and setup-kolab I couldn't login to
kolab-webadmin with cn=Directory Administrator.  In
https://coders-home.de/kolab-webadmin-login-unter-centos-7-nach-installation-nicht-moeglich-632.html
I found the tip to enable apache access to LDAP with

,----
| setsebool httpd_can_connect_ldap=true
`----

After that I can login to kolab-webadmin and can create a user.
Can we use that Instead of "disable selinux" in the installation
instructions (source/installation-guide/preparing-the-system.rst)?
Or is that something that should be added to setup-kolab?

Proposed diff:

diff --git a/source/installation-guide/centos-community.rst b/source/installation-guide/centos-community.rst
index 14bd91a..778f135 100644
--- a/source/installation-guide/centos-community.rst
+++ b/source/installation-guide/centos-community.rst
@@ -42,4 +42,11 @@ Installation on CentOS
 
         # :command:`yum install kolab`
 
+7.  Enable apache to access LDAP (no need to disable selinux):
+
+
+    .. parsed-literal::
+
+        # :command:`setsebool httpd_can_connect_ldap=true`
+
 Continue to :ref:`install-setup-kolab`.
diff --git a/source/installation-guide/preparing-the-system.rst b/source/installation-guide/preparing-the-system.rst
index 61df8f0..280f18a 100644
--- a/source/installation-guide/preparing-the-system.rst
+++ b/source/installation-guide/preparing-the-system.rst
@@ -68,8 +68,8 @@ know what AVC denials occur so we can work on fixing the issue.
 
 .. WARNING::
 
-    The Kolab Web Administration Panel and Cyrus IMAP against the Kolab
-    SASL authentication daemon currently require SELinux **NOT**
+    Cyrus IMAP against the Kolab
+    SASL authentication daemon currently requires SELinux **NOT**
     enforcing the targeted policy.
 
 To view the current mode SELinux operates in, execute the following


Jochen

-- 
The only problem with troubleshooting is that the trouble shoots back.



More information about the devel mailing list