Re: A hack for LDAP supportCool if it works ..tho i have no ldap account anywhere n don't even know how to use it, lol 
But looks like today is communication day .. xmlprc + ldap on same day 
Re: A hack for LDAP supportAnd a bug-fix same day :)
I forgot to include a file (main.php) to first package. I updated package and could be downloaded with same link, but filename has changed (v0.02).
Re: A hack for LDAP supportNice hack... What might make this easier to implement (especially in a corp environment) is to come up with a routine that moves users from the XOOPS db to the LDAP db once they are approved (activated/or admin approved).
Any chance of keeping information stored in both places? Example, userid and pw are stored in LDAP and the rest in XOOPS db. This would be a hybrid approach but would make XOOPS code easier to maintain.
I don't know if this could be done but, modify XOOPS core to use both MySQL and LDAP where appropriate?
Re: A hack for LDAP supportMy current plans with LDAP support:
1. XOOPS will have two modes (as look from LDAP perspective):
i. LDAP disabled mode: Same as current XOOPS :)
ii. LDAP enabled mode: Authentication of some or all except admin will be from LDAP server [done]
2. There will be two type of users:
i. XOOPS MySQL users: passwords will be kept in MySQL.
ii. LDAP users: passwords will be kept only on LDAP (for security reasons). All other info will be kept on XOOPS db. [done]
3. There will be LDAP user checkboxes in user registration and Edit user pages. So admin and user can choose which user will authenticate from LDAP server. [I need help]
4. Also if an LDAP user tries to login without creating XOOPS profile, XOOPS will ask user, would you like to create an XOOPS LDAP user. [I need help]
After compleation of these tasks we can integrate LDAP support in Core of XOOPS. But I need help with registration forms etc.
I hope we can integrate LDAP support in RC3.0.5 
Re: A hack for LDAP supportI think nobody here really knows or uses LDAP, so i think your best bet would be:
Write LDAP routines with empty blocks saying what ya need it todo:
some_ldap function() {
do some stuff ......
/*
stuff ya dont know goes here:
here we need to insert this n that in db or check this
*/
keep going on....
}
---------
Also if possible, best bet would be to put all the ldap functions in include files, and then just include() into the XOOPS source.
Like this it'll be a bit more readable than being interlaced with the XOOPS code.
Once that done, i suggest you post the code here in a zip so everyone can check it out n figure out how to fix whats missing
A nice link to a LDAP tutorial would be cool ..at least for me 
..ive heard about it, n know more or less what it is, but never used it or tried to play with it. (i suppose IE/Opera dont support it, n theres no way to test it on win 9x/ME ?)
Cheers
Re: A hack for LDAP supportLDAP support project almost done, except a few problems and bugs.
I've released 0.04 version of (I guess) last alpha release. You can download again with same link.
There are two problems in file /XOOPSdir/user.php:
1. on function ask_ldap_user_create($uname) screen is not displayed as ordinary XOOPS screen. Images cannot be displayed because image URLs looks like:
http://127.0.0.1/xoops/themes//images/logo.gif
But it should be:
http://127.0.0.1/xoops/themes/xtheme/images/logo.gif
2. again in same function I would like to call
register_ldap_user($uname) function instead of
admin.php?bla bla bla
Would you please look user.php file and these problems and can you advise some corrections.
If I can correct these problems I can release a beta version and look for beta testers :)
Thank you for help
Best regards
Re: A hack for LDAP supportI am writing to say I used this module and I had to tweak it to get it to work. The login ID is not called uid but rather employeeNumber. That field might be good to set in preferences. Also... when I went back into preferences, the search name was not set, you might want to check your code to pull this back in.
I am editing your LDAP user exists but does not have an account part to create the account then redirect them. That is the better way, also made a user preference drop down to let them change their profile to LDAP enabled.
Re: A hack for LDAP support1. You may need to add $xoopsTheme global declaration under the function
2.
function ask_ldap_user_create($uname){
global $xoopsTheme;
include("header.php");
OpenTable();
echo "
Re: A hack for LDAP supportFor the logo, just add a global $xoopsTheme
The rest dont understand too much, ask ono
Just some points ... what if the admin switches to ldap enabled after users signed up, or the inverse, or if not in ldap mode n the user enters crap like n/a, none, etc ..maybe a one or the other setting?
And if not in ldap mode, everything should probably hidden .. no use to confuse normal users or admins.
At least i think the ldap part should be as discrete as possible in the code with not many calls being made to it if not enabled, since over 95% of all ppl wont even be using it.
Best would be if it could be a external class or a module, or a step by step hack .. not just: overwrite your files with this. Since if it's not integrated, it will be hard for somone to go seep through the code n figure out what's been added and not. Especially with each new version of xoops, unless each time you upgrade it.. and thats a pain in the butt too :o)
Document it, push it into classes or external functions/classe as much as possible, etc 
..anyways, just my suggestions, if anyone will be adding this into xoops, it'll be Onokazu.
And personally, i don't have a clue about ldap anyways
Re: A hack for LDAP supportI completely agree with you. I should isolate LDAP codes and core code. But I don't have too much knowledge with XOOPS in depth to make classes etc. Maybe I should give ldap functions to developers of XOOP, than they can integrate easier.
Another idea, if we can test and eliminate all bugs as soon as possible, we can put these codes in core of next release, maybe RC4 maybe RC3.0.5 maybe RC3.1.0. I don't know, you should decide. You know whole project, I can only look from my project's perspective.
But first I hope I'll release first beta version (all functions complated I aimed with many bugs) today. Than we'll discuss how should we develop these codes in deeper.
Re: A hack for LDAP supportOnokazu, thank you for your help, first one works perfect :)
But second one is not working :(
NO button gives "error on page" error message
YES button directs to ordinary blan registration page.
Re: A hack for LDAP supportmayday,
which version have you used?
I've release 4 alpha versions in 3 days. Most stable is 0.04, with this version nearly every functions working properly except some GUI related bugs. You can try this 0.04 version, you can download with same URL.
I hope I can solve these GUI related problems and I can release a beta version tomorrow.
Re: A hack for LDAP supportoops..i guess there are many mistakes in the codes.. 
change action='register.php' to action='user.php'
and
also change
location:user.php
to
location=\"user.php\"
i've not tested these at all...just writing them all here, so there may be more that needs to be fixed.
Re: A hack for LDAP supportI think the easies way to help would be to know how to use a ldap server localy to begin with :)
Have apache/php here on winME and mozilla installed .. but dont have a clue about ldap, so aint gonna be able todo much here to help since i dont understand it myself
One way to pull your code outta the core for now wwould be to put all your functions in a simple php file called ldap.php and then just include it when needed.
Like this the core would be abit more readable as to what ya changed or not.
| Stats | |
| Goal: | $100.00 |
| Due Date: | Nov 30 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $100.00 |
 |
|
