[X] The "/OldFiles" file could not be found or is not available. Please select another file.

Share

More
python ldap user environment Icon

python ldap user environment

beta

by madram


This is a scripting environment based on shellscripts and python modules that gives one the ability to manage users, groups and aliases in an ldap directory. It also provides configuration examples of how to use ldap for authenticating users with Linux.


http://pylue.sourceforge.net





Separate each tag with a space.

Release Date:

2005-02-15

Topic:

Operating System:

License:

Translations:

Intended Audience:

Programming Language:

Registered:

2004-08-14

Ratings and Reviews

Be the first to post a text review of python ldap user environment. Rate and review a project by clicking thumbs up or thumbs down in the right column.

Project Feed

  • pylue 0.9.8 file released: userscripts-0.9.8a-20050215.tar.gz

    Changelog (starting, very late, on Friday, the 23rd of July in 2004) 2004-07-23 FRI - version 0.9.1 I decided to show my work to the public by uploading it to my .mac Website. I know there is still a hell of a lot to do but it was necessary to upload it anyways. I mean, how can I expect myself to do further work on this if I'm not even willing to show it? 2004-08-14 SAT - version 0.9.2 Well, to be honest I did a lot to the modules since my last entry. I think I can say now that there are no modules left with hardcoded ldap schema or configuration information. Everything should be dynamically by now. I decided to put the framework under GPL and present it to the public on sourceforge.net. 2004-08-22 SON - version 0.9.3 I did not really do any changes on the modules and stuff, but rather concentrated on the documentation instead. I added a README, an INSTALL and a BUGS file to document how the system works, how it is installed and what bugs to expect when using it. Today I'm uploading all this and then afterwords I will open a bottle of Champagne with my beautiful girlfriend. 2004-12-14 TUE - version 0.9.4 changed the following scripts: * addgroupmember.sh * delgroupmember.sh Put the call to (re)create the mailinglist within the for-loop that runs through the given users. * addusr2grp.sh * delusrfromgrp.sh Fixed the check on the return code of module addusr2grp-ldap.py so that the scripts also look for SUCCESS as opposed to only SUC and AMB. * emaillists.sh Corrected some typos in the created files. 2004-12-21 TUE - version 0.9.5 changed nearly all shellscripts in that they now accept scripted as a paramter to supress output to the console. Before the scripts used to expect console in case where output to the console was wanted. I think this just makes more sense. Also, when scripted is given, the helper-sh scripts are started with that parameter too. Because of that I had to change all helper-sh scripts as well. They used to expect script as a paramter. * scriptsconfig.def added some new options and removed one in the shellscripts config file. + IMMUFILES used by the setperms.sh script. It is a list of files that should be kept with acces rights set by IMMURIGHTS and owned by IMMUOWNER. + IMMUOWNER is the owner of the IMMUFILES + IMMURIGHTS is the octal value of the access rights for the IMMUFILES + IBOXSUBDIR a list of mailboxes that should be present below the Inbox current: Drafts Sent Spam Trash Viren + NOLINKFOR is used as a list of names for which no links in the users shared folder should be created. The names in this list are for groups that do not have a common filespace. + REPORTSDIR points to the directory where all statistics and reports about the user environement shall be kept. At the moment only getsysinfo.sh uses this directory for it's du-reports. + USRSHRFLDARIGHTS is a new option that is used to define the access rights of the shared folder in the users homedirectory Changed the option names for SHRUID and SHRGID to USRSHRFLDUID USRSHRFLDGID - SCRIPTSPATH was deleted. It was only there for compatibility reasons and has not been used in month. * chkshared.sh Now uses the variable NOLINKFOR as a list of groups where no link should be created for - see above under scriptsconfig.def I changed the order of the two cascaded for-loops that are used to determine if a link is to be created. I used to loop through the filesystem and doing an ldap lookup for every group in the shared folder. Now it's the opposite around. I loop through the ldap-groups ones. This should bring a significant performance boost when doing checks on the shared folder. * chkmaildir.sh instead of checking and creating the current 5 subdirs to the inbox I choose to make this an option (IBOXSUBDIR) in the scriptsconfig.def file and a loop that runs through them. * maildirusage.sh I hate this scripts, it's just not good. Anyway I made sure it uses variables from scriptsconfig.def and not hardcoded stuff. * setperms.sh Now uses the variable SHAREDDIR from scriptsconfig.def as opposed to hardcoded /export/shared. This option is used as a starting point for the search for IMMUFILESs. 2004-12-21 WED - version 0.9.5 I changed the emaillists.sh script so that it can be started without a groupname. In this case the script will check every email list. I brought all scripts up to version 0.9.5 and made sure all shellscripts exit with a zero return code and all descriptions are meaningful. 2004-12-27 MON - version 0.9.5 Bugfixed the newuser.sh script. There was an error in the query for console that made the script always afail :-( I also changed the way the tarball is created. It now makes assumes / as the starting point, making it possible to untar the /usr/scripts and /etc part directly to the right location. And, finally, I moved all files - including this - to /usr/share/doc/userscripts with a link from /usr/scripts/documentation 2004-12-28 TUE - version 0.9.6 This is the final release version. I think there should not be any hardcoded fragments left in the whole system and I could not find any obvious errors - Although, as anyone who studied software engineering knows, not seeing any errors does not mean there are no! What truly makes this release special, is that I changed the way it is distributed. There are now RPM- DEB and MacOS X Packages available along with the normal tarball. 2004-12-29 WED - version 0.9.6 I changed the way the system checks for groups a user belongs to. I used to do this with a python module that would iterate through all the sharegroups in the ldap tree. This was a bad idea as it took for ages and would not reflect the actual system state - where a user might belong to groups like wheel an so. Therefor this check is now done using the system program id: id -Gn <USERNAME> Changed the VALIDPROTONAMES option from /etc/scriptsconfig.def so that it now reads a file from the Protocol directory instead of holding the valid protocol names directly. That makes it possible for a company with different independent file servern and protocols to still share the same configuration file. 2005-01-05 TUE - version 0.9.7 I had to hardcode the NOLINKFOR option again. This option is used to specify groups for which no links should be created in the users home directory. The reason I had to hardcode this again (I wanted to make this an option in the scriptsconfig.def file) is that I do not know how to make bash accept a list for a casae query from a variable. I tried every way I could imagine but the shell would always ignore the list - so, if anyone finds out how to make the shell accept a construct like this: NOLINKFOR="Group1 Group2" case "$CURGROUP" in $NOLINKFOR) # do something ;; *) # do something else ;; esac please let me know. 2005-01-14 TUE - version 0.9.7a Ii did a bit bugfixing on the setperms.sh and emaillists.sh script. The name of the Group-Members.txt file is now taken from the scriptsconfig.def file. 2005-01-20 THU - version 0.9.8 I added a check to all shell scripts to see if the user did configure the system for its needs. If the file /etc/scriptsconfig.def was not edited - the user did not check the file and deleted the line starting with #Unconfigured! - the scripts will grep this line and exit. 2005-01-23 SUN - version 0.9.8 I also changed the way the destructive params like homealso or destructive are used in the scripts: delsysgroup.sh deluser.sh delgroup.sh chkhome.sh. These scripts can now take only either the scripted _OR_ the destructive param as I think those two are mutually exclusive. Moreover I changed a very important part of the newuser.sh script in that it now checks for a new configuration param from the scriptsconfig.def file. The new option is IMAPSERVER and can either be the short hostname of the imap server in use or NONE. In the latter case the newuser.sh script will not create maildirs for that user. If the IMAPSERVER option holds a hostname newuser.sh and chkmaildir.sh will only create maildirs if the current hostname is equal to the content of that option. The second new option is SMTPSERVER and should point to your sites smtp server. This option is - at the moment - only meaningfull if you do not store your aliases in the ldap. The newuser.sh script will check if the current server is the smtp server and if so and the aliases are stored in the flat alias file will put the alias for the new user in that file. 2005-02-15 TUE - version 0.9.8a The calling shell-scripts now check if the python modules return DWN. DWN means the LDAP server is down, which I now consider a fatal error, after which the script will stop and exit with an errorcode of 1.

    posted 1787 days ago

  • File released: /pylue/0.9.8/userscripts-0.9.8a-20050215.tar.gz

    posted 1787 days ago

  • pylue 0.9.1a file released: userscripts-dist-20041214.tar.gz

    Changelog (starting, very late, on Friday, the 23rd of July in 2004) 2004-07-23 FRI I decided to show my work to the public by uploading it to my .mac Website. I know there is still a hell of a lot to do but it was necessary to upload it anyways. I mean, how can I expect myself to do further work on this if I'm not even willing to show it? 2004-08-14 SAT Well, to be honest I did a lot to the modules since my last entry. I think I can say now that there are no modules left with hardcoded ldap schema or configuration information. Everything should be dynamically by now. I decided to put the framework under GPL and present it to the public on sourceforge.net. 2004-08-22 SON I did not really do any changes on the modules and stuff, but rather concentrated on the documentation instead. I added a README, an INSTALL and a BUGS file to document how the system works, how it is installed and what bugs to expect when using it. Today I'm uploading all this and then afterwords I will open a bottle of Champagne with my beautiful girlfriend. 2004-12-14 TUE changed the following scripts: * addgroupmember.sh * delgroupmember.sh Put the call to (re)create the mailinglist within the for-loop that runs through the given users. * addusr2grp.sh * delusrfromgrp.sh Fixed the check on the return code of module addusr2grp-ldap.py so that the scripts also look for SUCCESS as opposed to only SUC and AMB. * emaillists.sh Corrected some typos in the created files.

    posted 1850 days ago

  • File released: /pylue/0.9.1a/userscripts-dist-20041214.tar.gz

    posted 1850 days ago

  • File released: /pylue/0.9.1/userscripts-dist-20040822.tar.gz

    posted 1964 days ago

  • pylue 0.9.1 file released: userscripts-dist-20040822.tar.gz

    Changelog (starting, very late, on Friday, the 23rd of July in 2004) 2004-07-23 FRI I decided to show my work to the public by uploading it to my .mac Website. I know there is still a hell of a lot to do but it was necessary to upload it anyways. I mean, how can I expect myself to do further work on this if I'm not even willing to show it? 2004-08-14 SAT Well, to be honest I did a lot to the modules since my last entry. I think I can say now that there are no modules left with hardcoded ldap schema or configuration information. Everything should be dynamically by now. I decided to put the framework under GPL and present it to the public on sourceforge.net. 2004-08-22 SON I did not really do any changes on the modules and stuff, but rarther concentrated on the documentation instead. I added a README, an INSTALL and a BUGS file to document how the system works, how it is installed and what bugs to expect when using it. Today I'm uploading all this and then afterwords I will open a bottle of Champagne with my beautiful girlfriend.

    posted 1965 days ago

  • Code committed

    Anonymous committed patchset 1 of module CVSROOT to the python ldap user environment CVS repository, changing 11 files

    posted by nobody 1970 days ago

  • Forum thread added

    Anonymous created the Welcome to Developers forum thread

    posted by nobody 1970 days ago

  • Forum thread added

    Anonymous created the Welcome to Help forum thread

    posted by nobody 1970 days ago

  • Forum thread added

    Anonymous created the Welcome to Open Discussion forum thread

    posted by nobody 1970 days ago

Rate and Review

Be the first person to add a text review.

Would you recommend this project?






<

Related Projects

python ldap user environment Actions

Thanks for your rating!

Would you also like to write a review?





Skip Review

Thanks for your review!

Get credit for your review by logging in via OpenID. Click your account provider:

No Thanks