We were originally using Apple OS X Server as our LDAP store for our Alfresco instance.
Apple’s OS X Server uses OpenLDAP but adds custom schema for many things including users and groups. As a result we ended up using the
description LDAP attribute for Alfresco’s
We’ve since migrated to a generic OpenLDAP server (with a bit of our own custom schema) so we’re now able to use the more common and unchanging
cn attribute for the group id.
When we change
ldap-synchronisation.properties Alfresco imports the new groups properly but group permissions on spaces will retain the old group name so we need to change those to use the new
What we did was to create a temporary table in the Alfresco database, import the mapping of the
cn attribute to the
description attribute, then run a query to replace the old authorities with the new.
The following assumes Alfresco version 3.x.
Create the Temp Table
Import the LDAP Group Data
We used phpLDAPAdmin to export our groups subtree as CSV with only the
description attributes, then imported that file into the
t_ldap_groups table just created.
Replace the Old Authorities
I’m by no means an SQL expert but the query below does the following:
GROUP_from the current stored group long name
- Searches the temporary LDAP table for that group long name and corresponding group short name
- Updates the
GROUP_group short name
In Alfresco 2.x the authority is stored directly in the
alf_access_control_entry table as well so the update statement would be a bit more complicated.
Drop the Temp Table
DROP TABLE t_ldap_groups;
So far we haven’t had any adverse effects on our development server doing things this way but if anyone has a better method or potential issues with this one let us know.
It seems the time has come that I start making my thoughts known to whoever might be listening out there via the sometimes informative, sometimes controversial, often ridiculous medium of blogging.
After investigating several services and open source blogging web apps I’ve chosen to give WordPress.com a try as you can no doubt see if you’re reading this post.
I was leaning towards a hosted service from the start as I have grown very weary of maintaining servers and apps in my ‘old age’. Google’s Blogger (formerly Blogspot) and WordPress.com emerged as the two best candidates for a ready-to-use, free, hosted blog platform that suited my needs.
In the end I went with WordPress for a couple of reasons:
- I don’t plan to ever have ads.
- It seems to be widely used.
- Most WordPress blogs I saw seemed to be cleaner than Blogger’s (whether that’s purely a function of the themes or the type of creators each attracts I’m not sure)
- I can deploy it myself if the need arises.
- Alfresco supports posting content to WordPress out of the box.
It shouldn’t be too tough to switch if I can’t stand it, but so far I do like the service/app.
I’d imagine the content here will consist primarily of brain dumps about enterprise java, open source integration, general technology thoughts, and the occasional rant. I’ll apologize in advanced for the terrible vocabulary and grammar.
I hope it’s useful to someone.