Effy's Blog

My last post was dedicated to using LDAP as security back end for Jenkins-CI . Now I would like to present a process of enabling the same security for my favourite wiki implementation ... JAMWiki . This post refers to version 1.2.0 . I believe that it is a shame, that this is not well documented. There is a commented-out section in config xml (WEB-INF/applicationContext-security.xml), but it does not work out of the box as I have hoped for and it's modification is not an easy task for someone not familiar with spring security. That is why I wrote this post. What I wanted to achieve was to connect the JAMWiki's security (users and roles) to my LDAP, that was presented in my last post. As it is always easier to manage users on the same place. This process is described on JAMWiki's web , but it is certainly not in a copy-paste form and it took me quite some time to modify into working piece of code.

I recently deployed Jenkins CI on my personal server. The hardest question was what security solution should I use. As title of this post may have suggested I have chosen to use the infrastructure I already have ... LDAP. Now I would like to describe, how easy this configuration is and how it works. My LDAP structure My base dn is dc=effy,dc=cz. And it contains two organizationUnit s ... ou=people (to hold users) and ou=groups (to hold user roles). Groups (Roles) are presented by objectClass groupOfNames , they are identified by cn . People (Users) are of objectClass inetOrgPerson , thus identified by uid .