<div dir="ltr"><div>Since the auth change I don't have any ideas on how LDAP works to be honest (and I have no LDAP of my own to test against, or remember how it works).<br><br>I would look in the PHP and see where they are used. <br>
</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Dec 19, 2012 at 4:41 PM, Ron Mitchell <span dir="ltr"><<a href="mailto:ronm@mitchellmedia.co.uk" target="_blank">ronm@mitchellmedia.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dave<br>
to be honest these were just notes I made when installing on a college<br>
server a while back. But a few thoughts/comments...<br>
<br>
Yes I think curly brackets could be used previously but I'm not sure if that<br>
has changed now that the settings are stored in a separate ldap table<br>
<br>
I don't know what knownname is for either. That column in the database is<br>
set to not allow nulls but I couldn't find where it is used. It didn't exist<br>
in the sitedetails table where ldap details were stored previously.<br>
<br>
The ldap code is now inside \library\Xerte\Authentication\Ldap.php so you<br>
might find some pointers there but I would try different settings via<br>
management.php before messing with that.<br>
<br>
If you have your moodle working with ldap the settings you use there should<br>
map directly to the xot ldap table. Alternatively you could always use<br>
moodle for authentication? That's detailed in the readme in the root of the<br>
zip.<br>
<br>
Perhaps Pat or David from the dev team might comment further.<br>
<br>
HTH<br>
Ron<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:xerte-bounces@lists.nottingham.ac.uk">xerte-bounces@lists.nottingham.ac.uk</a><br>
[mailto:<a href="mailto:xerte-bounces@lists.nottingham.ac.uk">xerte-bounces@lists.nottingham.ac.uk</a>] On Behalf Of David Perry<br>
Sent: 19 December 2012 16:15<br>
To: 'Xerte discussion list'<br>
Subject: [Xerte] Re: Xerte Online Toolkit v1.9 - LDAP settings for a Novell<br>
network<br>
<br>
Ron<br>
<br>
This is based on a clean install (the upgrade didn't completely work).<br>
<br>
Your example is interesting, thanks.<br>
<br>
We can't bind to a specific ou= because our users are scattered around them<br>
based on which physical site and department they are in, all we can say is<br>
'they are somewhere within o=hull_coll'. My colleague remember having used a<br>
curly brackets notation previously to invoke sub-context searches, but not<br>
sure here if you can just say '{cn=}'.<br>
<br>
What does knownname mean? What should be there?<br>
<br>
And is your example for hooking up to an AD system? Does it search<br>
sub-contexts? If so we can try and get access to an AD server.<br>
<br>
And what's this sAMAccount name for in ldap_filter_attr?<br>
<br>
Thanks,<br>
Dave<br>
<br>
David Perry<br>
eLearning Technologist, eLearning Team (L34 - Library) Hull College Group<br>
Wilberforce Drive, Queen's Gardens, Hull<br>
HU1 3DG<br>
Extension 2230 / Direct Dial 01482 381930<br>
<br>
<br>
<br>
<br>
<br>
* * * Think about the environment - Do you really need to print this<br>
email?>>> "Ron Mitchell" <<a href="mailto:ronm@mitchellmedia.co.uk">ronm@mitchellmedia.co.uk</a>> 19/12/2012 15:58 >>> Did<br>
you upgrade or create a new install?<br>
If you upgraded run upgrade.php to transfer ldap details from the site<br>
details table to the ldap table.<br>
Then try different details via management.php with that open in one browser<br>
and testing login in a different browser.<br>
Check that the details are being stored in the ldap table.<br>
<br>
I don't know the specifics of Netware but the doc attached might help with<br>
the differences from 1.7 to 1.9.<br>
<br>
HTH<br>
Ron<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:xerte-bounces@lists.nottingham.ac.uk">xerte-bounces@lists.nottingham.ac.uk</a><br>
[mailto:<a href="mailto:xerte-bounces@lists.nottingham.ac.uk">xerte-bounces@lists.nottingham.ac.uk</a>] On Behalf Of David Perry<br>
Sent: 19 December 2012 15:32<br>
To: <a href="mailto:xerte@lists.nottingham.ac.uk">xerte@lists.nottingham.ac.uk</a><br>
Subject: [Xerte] Xerte Online Toolkit v1.9 - LDAP settings for a Novell<br>
network<br>
<br>
Hi all<br>
<br>
Has anyone got a working set of LDAP settings for a Netware-based network?<br>
We've left the bind password blank as we don't authenticate to our LDAP<br>
servers, but not sure what to set the filter and other bind values for - we<br>
use cn for username, knownAs for the full name, dn for their location within<br>
the tree (e.g. cn=username,ou=admin,ou=site,o=hull-college) and have set the<br>
basedn to be o=hull_coll (the same as we do for moodle).<br>
<br>
This is for the latest version. The previous one we were running had the<br>
LDAP code hacked to ignore the database settings for it, but it doesn't look<br>
as straightforward to do this in the latest version.<br>
<br>
<br>
Thanks,<br>
Dave<br>
<br>
David Perry<br>
eLearning Technologist, eLearning Team (L34 - Library) Hull College Group<br>
Wilberforce Drive, Queen's Gardens, Hull<br>
HU1 3DG<br>
Extension 2230 / Direct Dial 01482 381930<br>
<br>
<br>
<br>
* * * Think about the environment - Do you really need to print this email?<br>
<br>
<br>
**********************************************************************<br>
This message is sent in confidence for the addressee only. It may contain<br>
confidential or sensitive information. The contents are not to be disclosed<br>
to anyone other than the addressee. Unauthorised recipients are requested<br>
to preserve this confidentiality and to advise us of any errors in<br>
transmission. Any views expressed in this message are solely the views of<br>
the individual and do not represent the views of the College. Nothing in<br>
this message should be construed as creating a contract.<br>
<br>
Hull College owns the email infrastructure, including the contents.<br>
<br>
Hull College is committed to sustainability, please reflect before printing<br>
this email.<br>
**********************************************************************<br>
<br>
<br>
<br>
_______________________________________________<br>
Xerte mailing list<br>
<a href="mailto:Xerte@lists.nottingham.ac.uk">Xerte@lists.nottingham.ac.uk</a><br>
<a href="http://lists.nottingham.ac.uk/mailman/listinfo/xerte" target="_blank">http://lists.nottingham.ac.uk/mailman/listinfo/xerte</a><br>
This message and any attachment are intended solely for the addressee and<br>
may contain confidential information. If you have received this message in<br>
error, please send it back to me, and immediately delete it. Please do not<br>
use, copy or disclose the information contained in this message or in any<br>
attachment. Any views or opinions expressed by the author of this email do<br>
not necessarily reflect the views of the University of Nottingham.<br>
<br>
This message has been checked for viruses but the contents of an attachment<br>
may still contain software viruses which could damage your computer system:<br>
you are advised to perform your own checks. Email communications with the<br>
University of Nottingham may be monitored as permitted by UK legislation.<br>
<br>
This message and any attachment are intended solely for the addressee and<br>
may contain confidential information. If you have received this message in<br>
error, please send it back to me, and immediately delete it. Please do not<br>
use, copy or disclose the information contained in this message or in any<br>
attachment. Any views or opinions expressed by the author of this email do<br>
not necessarily reflect the views of the University of Nottingham.<br>
<br>
This message has been checked for viruses but the contents of an attachment<br>
may still contain software viruses which could damage your computer system:<br>
you are advised to perform your own checks. Email communications with the<br>
University of Nottingham may be monitored as permitted by UK legislation.<br>
<br>
_______________________________________________<br>
Xerte mailing list<br>
<a href="mailto:Xerte@lists.nottingham.ac.uk">Xerte@lists.nottingham.ac.uk</a><br>
<a href="http://lists.nottingham.ac.uk/mailman/listinfo/xerte" target="_blank">http://lists.nottingham.ac.uk/mailman/listinfo/xerte</a><br>
This message and any attachment are intended solely for the addressee and<br>
may contain confidential information. If you have received this message in<br>
error, please send it back to me, and immediately delete it. Please do not<br>
use, copy or disclose the information contained in this message or in any<br>
attachment. Any views or opinions expressed by the author of this email do<br>
not necessarily reflect the views of the University of Nottingham.<br>
<br>
This message has been checked for viruses but the contents of an attachment<br>
may still contain software viruses which could damage your computer system:<br>
you are advised to perform your own checks. Email communications with the<br>
University of Nottingham may be monitored as permitted by UK legislation.<br>
<br>
<br>
_______________________________________________<br>
Xerte mailing list<br>
<a href="mailto:Xerte@lists.nottingham.ac.uk">Xerte@lists.nottingham.ac.uk</a><br>
<a href="http://lists.nottingham.ac.uk/mailman/listinfo/xerte" target="_blank">http://lists.nottingham.ac.uk/mailman/listinfo/xerte</a><br>
This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.<br>
<br>
This message has been checked for viruses but the contents of an attachment<br>
may still contain software viruses which could damage your computer system:<br>
you are advised to perform your own checks. Email communications with the<br>
University of Nottingham may be monitored as permitted by UK legislation.<br>
</blockquote></div><br></div>