[commits] [Wiki] changed: GroupLdapMigration
Wiki Guest
wikiguest at horde.org
Fri Mar 1 08:05:21 UTC 2019
guest [95.90.223.65] Fri, 01 Mar 2019 08:05:21 +0000
Modified page: https://wiki.horde.org/GroupLdapMigration
New Revision: 2
Change log: Wrong wiki markup sorry
@@ -1,26 +1,26 @@
-h1. Migrating an existing horde installation's group from SQL to LDAP
++ Migrating an existing horde installation's group from SQL to LDAP
-h2. Manually
+++ Manually
I strongly suggest you don't play around in production!
-h3. Basics
++++ Basics
- Configure a separate vhost each for the db-based and the sql-based setup
- create conf-{sqlvhost}.host.com.php and
conf-{ldapvhost}.host.com.php each containing only the php tag and all
$conf['group'] stuff.
- use the docs on how to setup horde for ldap groups.
- ensure both are basically working (create some bogus group and add
some user in each backend)
- Now open https://{host}/horde/admin/groups.php or
https://{host}/admin/groups.php in each site.
- Create all the missing groups in the ldap backend. add all the
missing users.
-h3. Permissions
++++ Permissions
(assuming SQL backend) select * from horde_perms where perm_data
like "%groups%";
Each permission assigned to a group by numeric group id must be
cloned to be used by the ldap group backend.
Best use the group admin screen.
Do not attempt to edit the perms using an sql statement.
-h3. Shares
++++ Shares
(assuming sharesng sql backend is used)
Find any apps using sharesng shares
mysql> show tables like "%sharesng_groups%";
@@ -34,12 +34,12 @@
Create a corresponding entry with the same perms.
-h3. Cache
++++ Cache
Clear horde group cache and horde shares cache once you're done.
-h2. By script
+++ By script
TBD
More information about the commits
mailing list