Hi guys .. am running koha 3.16 (using debian 7 packages) however I am
unable to get ldap authentication working I have setup the ldap
paremeters in /etc/koha/site/opac/koha-conf.xml
1
localhost
ou=People,dc=example,dc=edu,dc=ng
0
1
1
Which is weird. That is the right base dn for users.. same DN works with
dspace on same ldap server and authentication works on that smoothly. Is
there a way I can see logs on how koha tries to bind with ldap? i.e the
entries it sends to bind with the ldap server.. maybe that might be a
good st
One thing which is not quite clear from the documentations am reading is
where the location for the /koha-conf.xml file should be.. most docs say
it should be in /etc/koha .. however when I checked my debian koha
install the file is located at /etc/koha/sites/library/ (which is where
I inputted
r isn't allowing anonymous bind and search,
since I would never allow that on my server if I didn't have to. Do
you provide something like a rootdn and password to dspace for it to work?
On Thu, Feb 19, 2015 at 8:08 AM, Bobby <mailto:bigbrov...@gmail.com>> wrote:
One
o work?
On Thu, Feb 19, 2015 at 8:08 AM, Bobby mailto:bigbrov...@gmail.com>> wrote:
One thing which is not quite clear from the documentations am
reading is where the location for the /koha-conf.xml file should
be.. most docs say it should be in /etc/koha .. however when I
chec
something like a rootdn and password to dspace for it to work?
On Thu, Feb 19, 2015 at 8:08 AM, Bobby mailto:bigbrov...@gmail.com>> wrote:
One thing which is not quite clear from the documentations am
reading is where the location for the /koha-conf.xml file should
be.. most docs s
Hi guys, I am experiencing some erratic behavior getting koha to talk to
our ldap server. I am trying setup where koha updates existing user details
(mainly passwords) but not replicate. This way only users created on the
koha server are able to authenticate since the userid on koha is the same
as
