Re: LDAP Library v0.5-beta1 releasedGreat 
I'm not a developer but realy think it would be nice to develop that kind of module.
Developers of the XOOPS world unite and help this guy :)
Great idea realy
Re: LDAP Library v0.5-beta1 releasedhello
what are differences between yours and pemen's one
have your been aware of it ?
marco
Re: LDAP Library v0.5-beta1 releasedYes I am aware of pemen's work. In fact we alreay have some plans on collaborating - nothing definitive yet though.
Pemen's module uses an existing LDAP directory and realizes authentication for XOOPS. It does not allow you to store data in the directory like in the MySQL-DB (ok, the last release added synchronizing of some data).
LibLDAP allows you to store any XOOPS object (users, groups ... forum posts) in LDAP and even to keep the objects in sync for both data backends if you need this.
So we are working on the exact opposite areas of LDAP integration.
The module I'm currently working on is in fact a LDAP enabled registration for XOOPS (which was the whole point of writing LibLDAP for me). That would complement pemen's work and cries for collaboration.
Re: LDAP Library v0.5-beta1 releasedThanks for your contribution!
This is a beta1 release, does this mean you're looking for testers? Any specific testing areas/environments you'd like feedback on? What are you still working on, and what is still to come? Will this be a stable release?
Pemen will be working on the XOOPS Authentication layer for XOOPS 2.3, maybe you two can join forces there too?
Lots of questions, sorry 
Herko
Re: LDAP Library v0.5-beta1 releasedNothing to be sorry for - I appreciate any feedback. The beta status means, that it works for me on my own server (apache2, php5) on the current XOOPS 2.0. I have done no tests with older versions, on other PHP-versions or even other Linux Distros (Debian and Gentoo tested).
Before I declare this stable I'd like at least some success stories from independent sources. So ... test, test, test!
The next steps for the module will be some testing the hard way as I'm writing a registration module on top of it and maybe converting the module into a core patch (pemen seems to like that idea) with tighter integration into XOOPS (enable gethandler to call LDAP handlers, make the repository connection a singleton ...). That depends on wether the core developers want the code in XOOPS. As long as I work on my own a module is easier to maintain that a patch.
By the way - is there some interest for a paid membership registration module?
Further down the road I want to improve the attribute mapper, which at the moment is only a text file, by getting it into the DB.
The biggest feature planned is schema integration. At the moment I only have a text file, that maps LDAP attributes to XOOPS data types (XOBJ_DTYPE...). That doesn't scale very well and the information is already there in the schema, where all attributes have data types. If LibLDAP could read that information and automatically map them to XOOPS data types, the module could adapt to any environment without writing the mapper by hand each time.
What really would be helpful to me, as I still consider myself a XOOPS newcommer, are some information on how to integrate the code better into XOOPS. I am sure, there are several great features I haven't used that would have made my life a lot easier. Also if someone finds bugs or has good ideas for improvement - bring it on.
Re: LDAP Library v0.5-beta1 releasedIn readme.txt :
Quote:
If you use XoopsUserHandler and a LdapHandler on a XoopsUser-Object all the object data gets stored in both backends.
Re: LDAP Library v0.5-beta1 releasedMaybe I should have mentioned that 
The tests must be embedded into a complete XOOPS
page or started by hand. The test on XOOPS_ROOT_PATH is to make sure they get started in correct context. Oh, and you must have simpletest installed.
To automate that I've written myself another (not yet released module) that searches all over the directory structure and executes everything in directories that have the name simpletest_unit_tests (can be configured). Then it renders the output of all the test on one page. That's why I use a self written XoopsReporter to render it nice for XOOPS.
I haven't released this module as it is a very ugly hack and needs a lot of cleanups (my very first XOOPS module).
Now for a fast solution:
<?php
require_once "mainfile.php";
require_once('simpletest/unit_tester.php');
require_once('simpletest/reporter.php');
class XoopsReporter extends HtmlReporter
{
}
include XOOPS_ROOT_PATH . '/header.php';
// include here whatever test you want to call
include('modules/libldap/simpletest_unit_tests/test_ldapdn.php');
include XOOPS_ROOT_PATH . '/footer.php';
?>
Depending on where you place this file, you have to adapt the paths.
| Stats | |
| Goal: | $100.00 |
| Due Date: | Apr 30 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|
