Changes between Version 59 and Version 60 of Old/hNodes/cNodeVer3/dAssembly/e4NodesSetup

Timestamp:

Jun 28, 2013, 9:05:49 PM (11 years ago)

Author:

ParviK

Comment:

—

Old/hNodes/cNodeVer3/dAssembly/e4NodesSetup

@@ -624 +624 @@
 }}}
 
-7. Make sure you can access the service with admin credentials:
+7. Without the pid file, the start/stop script fail to start/stop the daemon. This can be resolved by editing the /etc/init.d/slapd file and search for the function start_slapd(). Add this to the last line of that function before it exits:
+
+pidof /usr/sbin/slapd > "$SLAPD_PIDFILE"
+
+8. Make sure it is running by checking that ldap server is listening on both ports:
+
+netstat -an | grep 389
+netstat -an | grep 636
+
+9. Stop the service:
+{{{
+   /etc/init.d/slapd stop
+}}}
+
+10. Import initial content (first group and account that will be used as administrators for the login service): This is a brief reasoning behind the entries in the ldif file. Please change the file as per your organizational needs.
+Each organizational unit(ou) has a PI who is the admin for the OU and a group which has all the accounts for the OU. So that is why your first organization and first acount have to conform to such a structure.
+
+OU admin can only manage accounts for that organization.
+Any person that is a member of sysadmin group in LDAP and admin group in login.yaml will be able to use ControlPanel of the ogs_login service to manage ALL accounts.
+
+11. Run the following commands. 
+{{{
+  cp /usr/share/slapd/DB_CONFIG /var/lib/ldap/
+  slapadd -l init.ldif -f /etc/ldap/slapd.conf
+  chown openldap:openldap /var/lib/ldap/*
+}}}
+
+12. Start the service:
+{{{
+   /etc/init.d/slapd start
+}}}
+
+13. Make sure you can access the service with admin credentials:
 {{{
    ldapsearch -x   -b "dc=orbit-lab,dc=org"  "objectClass=organizationalRole"