ldap_integration 6.x-1.0-beta3

New features
Bug fixes

Finally a new beta... with lots of new and fixed stuff... IMHO, this is really close to a v1.0 release... but that may be developer pride...so it needs more folks to kick it's tires first.

Installation

This release requires you to run the update.php process after updating the module files.

New Features/Functionality

See #1475272: 6.x-1.0 Release Candidate 1 Status for specific details. The highlights are:

  • A new ldapsync module that allows for bulk imports/cron based data sync of users from LDAP servers.
  • Support for defining settings and servers via a Features "module"
  • Support for Import/Export of settings via admin GUI
  • Modules refactored to use ldap.core.inc common functions
  • Various modules now have more API hooks for localized support (see [module].api.php files for details)
  • Full read/write support for Content Profile module
  • Modules have strong checks for duplicate names and e-mail conflicts to keep with Drupal account practices.
  • Support for Persistent User IDs to allow for definitively identifying users who's name, e-mail, and/or user id has changed in LDAP. See the README-PUID.txt file for information.
  • Lots of internal optimizations like only returning required attributes and using cache to limit DB and LDAP calls.

ldap_integration 5.x-1.5

Security update

This release fixes:
* The LDAP integration module does not implement a confirmation pages for the LDAP server activation/deactivation which could cause a CSRF attack.
* A user defined server name is not properly escaped on the administration pages which might lead to a XSS attacks.
* The user's LDAP data is not properly access controlled before displaying it in the user profile pages which allows unauthorized view of the data.
* Some user management access rules are ignored during the authentication process.

ldap_integration 6.x-1.0-beta2

Security update

This release fixes:
* The LDAP integration module does not implement a confirmation pages for the LDAP server activation/deactivation which could cause a CSRF attack.
* A user defined server name is not properly escaped on the administration pages which might lead to a XSS attacks.
* The user's LDAP data is not properly access controlled before displaying it in the user profile pages which allows unauthorized view of the data.
* Some user management access rules are ignored during the authentication process.

ldap_integration 5.x-1.3

Bug fixes
Insecure

2007-08-22 kreaper

* ldap_integration/LDAPInterface.php: http://drupal.org/node/164049
Allow anonymous LDAP connect();

* ldapauth.module: http://drupal.org/node/164078
HTML fixes

* ldap_integration/LDAPInterface.php: http://drupal.org/node/158671
No longer initializing $ldap->server to "example.com"

2007-07-22 kreaper

ldap_integration 5.x-1.2

Insecure

Changes mainly on settings and built-in UI options; also many bugs fixed. See CVS commit notes for details

ldap_integration 5.x-1.1

Insecure

LDAP Integration 5.x.1.1 is now available for download. This is a maintenance release that fixed an important security issue.

Instructions
Download the full build and install it over the existing 5.x.1 build of ldap_integration. There are no database updates with this release, so it is not necessary to run update.php

Security Issue

ldap_integration 5.x-1.0

Insecure

Stable release of ldap_integration for Drupal 5.x.

New Features from 4.7 include

Limitations

ldap_integration 5.x-1.x-dev

Bug fixes

Development release for Drupal 5.x

This release contains primarily bug fixes now. It should be used instead of 5x-1-3/

Support for previous versions of this module may be extremely limited.

Subscribe with RSS Subscribe to Releases for LDAP integration