MySQL, data and LDAP access

MySQL Conference & Expo 2009

LDAP and RDBMs have often been opposed in the past with LDAP being the preferred service for fast frequent lookups, authentication and authorization, and RDBMs being the preferred service to write large data, updated frequently, mined some time to time.

But both technologies have some things in common: they are data stores and they are heavily used. And often, within an enterprise or a service provider, the data stored in the RDBMs is duplicated from the LDAP directory service (or vice-versa).

So there is an interest in sharing the data between RDBMs and LDAP. There are different ways to achieve this.

At the MySQL conference on April 20-23, 2009, we will be holding a BoF session to discuss how to make use of LDAP with MySQL databases, with Sun products : Sun Directory Server Enterprise Edition and OpenDS.

I hope to see you there.

Technorati Tags: , , , , , , ,

Hallo OpenDS ! Cześć OpenDS ! Hola OpenDS !

OpenDS, LDAP directory server. Open Standards, Open SourceCommunities are amazing. A day after we announced the Translation Community for the OpenDS project, we’ve already added 3 languages to the ones already set.

So I’m please to announce the availability in the Community Translation Interface, the OpenDS German translation project, the OpenDS Spanish translation project and the OpenDS Polish translation project.

OpenDS Gemeinschaft für Deutsch Übersetzung ist nun offen

OpenDS comunidad para la traducción español ya está abierto

OpenDS społeczność niemiecki tłumaczenie jest już otwarty

Disclaimer : those 3 translation above are computer generated, unlike the OpenDS community let translations !

General discussion are taking place on the G11N alias <g11n@opends.dev.java.net> but language specific mailing lists have been created to discuss in native languages the details:

  • For German : g11n_de@opends.dev.java.net
  • For Spanish : g11n_es@opends.dev.java.net
  • For Polish: g11n_pl@opends.dev.java.net

Please subscribe to the mailing lists if you intend to participate. And many thanks to the OpenDS community members that have already signed up.

Technorati Tags: , , , , ,

OpenDS 1.3.0-Build004 is now available

Opends Logo TagWe have just uploaded OpenDS 1.3.0-build004, built from revision 5184 of our source tree, to our promoted builds folder.

Note that this is a jump from OpenDS 1.3.0-build002 to OpenDS 1.3.0-build004. OpenDS 1.3.0-build003 was done with specific compilation to enable the MySQL Cluster NDB Backend, but not promoted with the regular builds.

The direct link to download the core server is: http://www.opends.org/promoted-builds/1.3.0-build004/OpenDS-1.3.0-build004.zip

The direct link to download the DSML gateway is: http://www.opends.org/promoted-builds/1.3.0-build004/OpenDS-1.3.0-build004-DSML.war

We have also updated the archive that may be used to install OpenDS via Java Web Start. You may launch that using the URL http://www.opends.org/promoted-builds/1.3.0-build004/install/QuickSetup.jnlp, or visit https://www.opends.org/wiki/page/OverviewOfTheQuickSetupTool for more information.

Upgrade from 1.0 or 1.2 is still broken, but upgrade from 1.3.0-build002 should work. However, a Flag Day was raised with revision 5134 which requires a rebuild of all indexes, or even better export the database to LDIF and re-import it.

Compared to 1.2.0, OpenDS 1.3.0-build004 contains the following new features and major improvements :

  • Assured Replication that provides stronger consistency and availability for replicated data
  • Supports Recurring Tasks allowing an administrator to schedule repeated tasks such as backups
  • Improves defaults settings and ergonomics for some server properties
  • Now builds VLV indexes during Import
  • A new internal ASN.1 encoding / decoding library that delivers better and more stable performances
  • Improves the Control Panel in various area
  • Now works well / better with IBM JVM
  • Full compliance with RFC 4518. Now DirectoryString matching fully supports UTF-8 characters
  • Supports languages specific matching rules for DirectoryStrings, for comparing and ordering, as well as support for indexing according to those rules
  • Provides better monitoring information for Replication
  • Full support for negotiating encryption through SASL and stacking encryption channels with TLS
  • Many performance improvements in the Core server and in Replication

Detailed information about this build is available at http://www.opends.org/promoted-builds/1.3.0-build004.

Major changes that have been incorporated since the last promoted build (OpenDS 1.3.0-build002) include:

  • Revision 5124 (Issue #3626) – Replace occurrences of grep, cat, etc. with built-in shell commands.
  • Revision 5125 (Issue #3896) – Fix an issue that prevented users from creating a sub-suffix with the Control Panel.
  • Revision 5126 (Issue #3826) – Fix an exception in the Control Panel that occurred if a node existed as a non-suffix node.
  • Revision 5129 (Issues # 3295 & 3899) – Fix an SNMP exception at startup and a resource issue on Windows platforms.
  • Revision 5130 (Issue #3297) – Fix a problem that caused localised answers to be rejected by certain commands.
  • Revision 5131 (Issue #3528) – Check that the start time entered for scheduled tasks has not already passed.
  • Revision 5132 – Remove keytool dependencie by using the keystore API, integrate Andy Wang’s IBM JVM/JDK changes, provide a Platform class to put platform and JDK version-specific code in a single location, provide APIs for core matching rules.
  • Revision 5133 (Issue #2616) – Fix an ldapsearch error when parsing command-line arguments.
  • Revision 5134 (Issue #3880) – Provide support for unicode characters in core matching rules.
  • Revision 5135 – Create a flag day for changes in revision 5134.
  • Revision 5136 (Issue #3555) – Refresh the DIT view in the Manage Entries menu of the Control Panel.
  • Revision 5138 (Issue #3582) – Fix a problem that caused reverts to fail with the error “no valid existing backup locations”.
  • Revision 5139 (Issue #3451) – Use a specific error message with ldapcompare if a specified file cannot be read.
  • Revision 5141 (Issue #3894) – Fix a potential data corruption issue when writing binary attributes/blobs.
  • Revision 5143 (Issue #3903) – Fix a problem that caused the “Start Server when the Upgrade has Completed” option to fail when upgrading using QuickSetup.
  • Revision 5145 (Issue #3455) – Correct an error that occurred when deleting a VLV index.
  • Revision 5147 (Issue #2793) – Ensure that incremental backups work as expected when an empty directory is specified.
  • Revision 5148 – Provide localized resource files.
  • Revision 5149 (Issue #3893) – Correct a problem that caused dsreplication enable between an OpenDS 1.2 server and an OpenDS 1.3 server to fail.
  • Revision 5150 & 5153 (Issue #3629) – Remove duplicate dsconfig error messages.
  • Revision 5151 (Issue #3793) – Provide the ability to create extensible indexes using dsconfig.
  • Revision 5152 (Issue #3910) – Ensure that Base64 encoding works with UTF-8 characters.
  • Revision 5155 (Issue #3908) – Fix a problems with ChangeNumber generators.
  • Revision 5156 (Issue #3892) – Make ACI evaluation optional when returning entries and references to clients.
  • Revision 5157 (Issue #3900) – Fix an error that occurred when importing / adding LDIF due to trailing spaces.
  • Revision 5158 (Issue #3505) – Fix a confusing ACI targetscope message.
  • Revision 5159 (Issue #2667) – Fix a problem that occurred when configuring VLV indexes with dsconfig.
  • Revision 5160 (Issue #3312) – Change aci and ds-cfg-global-aci equality matching rules to octetStringMatch instead of CaseIgnoreIA5EqualityMatchingRule.
  • Revision 5161 (Issue #2624) – Ensure that ldapsearch returns the correct return code when no password is provided.
  • Revision 5167 (Issue #3828) – Prevent a connection to the server from being tied up while waiting for the user to enter a password.
  • Revision 5168 (Issue #3321) – Fix an error raised during index creation and delete with dsconfig.
  • Revision 5169 (Issue #3270) – Ensure that ldappasswordmodify takes into account the password history count.
  • Revision 5171 (Issue #3251) – Fix the LDIFReader rejectLastEntry, which printed an incorrect entry.
  • Revision 5172 (Issue #2963) – Fix a problem that caused dsreplication status to display an incorrect value for missing changes.
  • Revision 5173 (Issue #3907) – Provide a pkg(5) delivery.
  • Revision 5174 (Issue #3904) – Complete the replication referral URL configuration regular expression implementation.
  • Revision 5175 (Issue #3748) – Ensure that all admin tools use 4444 as the default admin port.
  • Revision 5176 (Issue #3856) – Fix a problem that caused LDAPS connections to be logged as LDAP connections in the access log.
  • Revision 5177 (Issue #3673) – Ensure that the server checks for port availability on Windows.
  • Revision 5178 (Issue #3528) – Ensure that scheduled tasks check that the start time has not passed.
  • Revision 5179 (Issue #2965) – Add the missing-changes to cn=monitor for replication servers.
  • Revision 5180 & 5181 (Issue #3119) – Prevent a null pointer exception that occurred when disabling the referential integrity plugin.
  • Revision 5184 (Issue #3914) – Fix a problem that prevented the server state from being updated.

Technorati Tags: , , , , ,

Getting started with OpenDS Translations

OpenDS for the International crowd...Pavel Heimlich, the lead for the French translation for OpenDS, kindly posted an How To Guide for using CTI for the OpenDS community led translations, on the OpenDS Wiki.

If you’re interested in testing your translation skills with OpenDS messages, check the page, it gives a pretty good idea on how simple it is to use the tool… The hard part is really in providing good and consistent translation !

Technorati Tags: , , , , ,

Hello OpenDS ! こんにちは OpenDS ! Salut OpenDS !

OpenDS, the open source LDAP directory server in Java

[English] [Japanese] [French]

Dear OpenDS Community,

We are in the process of building the Translation Community for OpenDS, the open source LDAP Directory Service, and are calling for your participation. If you are interested in trying your skills as a translator a Quick start guide() is provided for you to get started with Community Translation Interface (CTI), a web based tool allowing community led translation.

As you may know, OpenDS 1.1 was translated into 7 languages. We would like your help now, to translate OpenDS 2.0 into the same 7 languages: Japanese, Traditional Chinese, Simplified Chinese, Korean, French, German, and Spanish. Today we’re starting with two languages (Japanese and French) but we will expand as contributors are lining up.

We would like to introduce our Language Leads for growing Community Translations.

Language Lead for Japanese Community Translation : Shinichi Hanaki <Shinichi (dot) Hanaki (at)Sun (dot) COM>. Contact Japanese Community Alias: g11n_ja@opends.dev.java.net

Language Lead for French Community Translation: Pavel Heimlich <Pavel (dot) Heimlich (at) Sun (dot) COM >

Contact French Community Alias: g11n_fr@opends.dev.java.net

Welcome Hanaki and Pavel.

Send your queries to g11n@opends.dev.java.net

Regards,

Shankar and Ludovic.


OpenDS コミュニティにご参加のみなさん、

私たちは、オープンソースの LDAP ディレクトリサービスである OpenDS

翻訳をコミュニティと共同で行うために、翻訳プロジェクトへのみなさんの参加をお待ちしてます。

もし、翻訳作業に関して興味がありましたら、以下のクイックスタートガイドを

参照してみてください。

https://cti.sunvirtuallab.com/community/help.jsp

このガイドでは、コミュニティの方が翻訳する際に実際に使っていただく、

web ベースのツール Community Translation Interface (CTI) について紹介しています。

ご存じのように OpenDS 1.0 では、英語以外に、日本語を含めて 7 つの言語でローカライズされていますが、

翻訳されている範囲はまだまだ限られており、今後、もっと多くの範囲を翻訳するために、

ぜひコミュニティの方にもお手伝いいただければと思っております。

まずは、手始めに日本語とフランス語に関して、コミュニティと共同での翻訳作業を考えてまして、

将来は、他の言語にも手を広げていく予定です。

日本人のコミュニティユーザー向けには、日本語のメーリングリストも用意されており、

メールアドレスは、g11n_ja@opends.dev.java.net になります。

コンタクト先:Shinichi Hanaki <Shinichi.Hanaki@Sun.COM>

(OpenSSO や OpenDS など、Sun のアイデンティティー関連製品の日本語ローカライズを

担当している者です。)

OpenDS の他のメーリングリストとは違って、ここでは日本語で気兼ねなくコミュニケーションを

とることができますので、日本語翻訳に興味のある方、また、翻訳は別にしても

OpenDS を実際お使いになられてる方、これから OpenDS を使ってみようと興味をもたれてる方も、

ぜひ、こちらのメーリングリストにご参加ください。

なにかわからないことなどございましたら、

g11n_ja@opends.dev.java.net 宛、もしくは上記コンタクト先アドレスへ

お問い合わせください。

みなさんのご参加をお待ちしてます。


Chers membres de la communauté OpenDS,

Nous sommes en train de mettre en place une Communauté de Traduction pour OpenDS, le serveur d’annuaire LDAP en logiciel libre, et faisons appel à votre participation. Si vous êtes intéressés par exercer vos talents de traducteur, vous trouverez ici un guide de prise en main de l’Interface de Traduction Communautaire (Community Translation Interface, CTI), un outil web pour faire de la traduction assistée par communauté.

OpenDS 1.1 a été traduit dans 7 langues. Nous aimerions de l’aide pour traduire OpenDS 2.0 dans ces 7 langues : Japonais, Chinois Traditionel, Chinous Simplifié, Coréen, Français, Allemand et Espagnol. Nous commençons dès aujourd’hui avec 2 langues (le Japonais et le Français) mais nous ajouterons les autres au fur et à mesure de la participation de traducteurs volontaires.

Permettez nous de vous présenter les responsables des différentes langues pour cette Traduction Communautaire naissante.

La traduction en Japonaise est conduite par Shinichi Hanaki <Shinichi (point) Hanaki (a) Sun (point) COM>, et un alias a été mis en place pour collaborer en Japonais autour des traductions : g11n_ja@opends.dev.java.net

La traduction Française est conduite par Pavel Heimlich <Pavel (point) Heimlich (a) Sun (point) COM>, et un alias a été mis en place pour discuter en Français sur les traductions : g11n_fr@opends.dev.java.net

Bienvenue à Hanaki et Pavel.

Pour toute information supplémentaire, contactez g11n@opends.dev.java.net

Cordialement,

Shankar et Ludovic.

Technorati Tags: , , , , , ,

Sun Directory Masters 2009 in Grenoble. Day 1.

Gecday1It’s been a busy day in the Grenoble Engineer Center with Directory Masters gathering from all over Europe and even Japan for two days of training on the coming releases of Sun Directory Server Enterprise Edition and Sun OpenDS Standard Edition.

For those two days, we’re hosting 30 sales, presales, architects, consultants from Sun and partner companies, immersed within the developers, architects, managers of the Directory Engineering team. This is a very good way for our guest to understand where the product is going and how to better sell it to customers, and for engineers to learn more about the real customers needs and problems to solve.

Today we’ve touched mostly the Directory landscape, our product roadmap, DSEE, deployments, performances, virtual directory features. Tomorrow will have more of an OpenDS flavor…

PS: To my Japanese friends, Moryia is not on the picture, but he’s in Grenoble 😉

Technorati Tags: , , , , , ,

OpenDS 1.3.0-Build002 is now available

Opends Logo TagWe have just uploaded OpenDS 1.3.0-build002, built from revision 5124 of our source tree, to our promoted builds folder.

The direct link to download the core server is: http://www.opends.org/promoted-builds/1.3.0-build002/OpenDS-1.3.0-build002.zip

The direct link to download the DSML gateway is: http://www.opends.org/promoted-builds/1.3.0-build002/OpenDS-1.3.0-build002-DSML.war

We have also updated the archive that may be used to install OpenDS via Java Web Start. You may launch that using the URL http://www.opends.org/promoted-builds/1.3.0-build002/install/QuickSetup.jnlp, or visit https://www.opends.org/wiki/page/OverviewOfTheQuickSetupTool for more i

nformation.

Detailed information about this build is available at http://www.opends.org/promoted-builds/1.3.0-build002.

Upgrade from 1.0 or 1.2 is still broken, but upgrade from 1.3.0-build001 should work.

Major changes that have been incorporated since the last promoted build (OpenDS 1.3.0-build001) include:

  • Revision 5052 (Issue #3823) – Correct an issue that caused the ds-privilege-name to cause an unchecked exception.
  • Revision 5054 (Issue #3832) – Provide ergonomics style settings for common server properties.
  • Revision 5055 (Issue #3831) – Add dsconfig support for a NullBackend.
  • Revision 5058 (Issue #3824) – Fix a null pointer exception that occurred if an offline import was done on an NDB back end.
  • Revision 5059 (Issue #3821) – NDB back end – do not normalize user provided DN forms when storing.
  • Revision 5060 (Issue #3816) – Fix a problem with replication when uppercase characters were included in DNs.
  • Revision 5061 (Issue #3851) – Force the monitor back end to return parent monitoring entries before their children.
  • Revision 5062 (Issue #3804) – Improve replication monitoring.
  • Revision 5064 (Issue #3678) – Prevent dsconfig from displaying the corresponding command when the –displayCommand option is not specified.
  • Revision 5066 (Issue #3860) – Fix a problem that prevented the server from finding a certificate in a JKS keystore if the alias contained uppercase characters.
  • Revision 5067 (Issue #2993) – Print the server’s runtime information in the logs when the server is started by the setup command.
  • Revision 5070 (Issue #3861) – Update the control panel to handle the new monitor attributes.
  • Revision 5071 (Issue #3764) – Fix a problem that caused the server to hang when the replication configuration was changed during a total update.
  • Revision 5072 (Issue #839) – Add a specific code for LDAPException handling.
  • Revision 5074 (Issue #3863) – Fix a dsconfig exception when trying to set the subject attribute in a Subject DN To User Attribute Certificate Mapper.
  • Revision 5079 – Fix indexed search scoping.
  • Revision 5083 (Issue #3525) – Ensure that attribute modifications are replicated for modDN operations.
  • Revision 5085 (Issue #3837) – Fix a problem that caused a subtree ldapsearch operation to return the same result twice.
  • Revision 5086 – Simplify index configuration and add configuration placeholders for future use.
  • Revision 5087 (Issue #3402) – Fix a replication conflict resolution issue that caused a failure to resolve a double mod_rdn of the same entry.
  • Revision 5088 (Issue #3714) – Ensure the ldapsearch returns exit code 10 when it receives a referral.
  • Revision 505091 (Issue #3873) – Fix a problem that caused certain commands to use the java.properties of other commands.
  • Revision 5095 (Issue #3300) – Fix a problem that prevented the server from starting if the back end of a replicated suffix was disabled.
  • Revision 5099 (Issue #3315) – Fix a problem that caused dsreplication initialize-all to return before the peer had completed initialization.
  • Revision 5104 (Issue #3853) – NDB back-end : make sure that blob handles are wired to their result sets to prevent out of order retrieval when iterating.
  • Revision 5105 (Issue #3886) – Fix an issue that prevented online import-ldif from using the skipfile.
  • Revision 5107 (Issue #3877) – Fix an unexpected error that occurred when enabling safe_data mode.
  • Revision 5110 (Issue #3854) – Fix various issues that caused uninstall to fail on Windows, due to log files.
  • Revision 5112 (Issue #3887) – Fix a problem that caused changes in the dynamic assured replication configuration to cause timeouts.
  • Revision 5113 (Issue #3829) – Fix a problem that occurred when dsreplication enable was used with “localhost” as the host name for –host1 and –host2.
  • Revision 5115 (Issue #3833) – Fix a corrupt index in a replication topology.
  • Revision 5117 (Issue #3827) – NDB back end : fix a problem that prevented the NDB back end from being enabled dynamically with dsconfig.
  • Revision 5119 (Issue #3889) – Allow replicas to know about the state of the other replicas in the topology.
  • Revision 5122 (Issues #3884 and 3867) – Fix two issues that prevented GSSAPI SASL authentication from working as expected.

Technorati Tags: , , , , ,

OpenDS, Sun Labs and Java teams collaborate on performances

Opends Logo TagIn the past months, Matthew Swift, OpenDS core server lead developer, has been focusing most of his work on improving OpenDS server’s performances, trying to leverage as many tools as he could.

DukewithhelmetSometime, tools are not enough, and Matt started to discuss with Laurent Daynes, researcher on multitasking virtual machines and also based in the Sun Grenoble Engineering Center, about some strange behaviors of the JVM when trying to benchmark OpenDS with huge databases and caches. A few weeks after, Tony Printezis, expert in the Garbage Collector, came to Grenoble and got interested in our project and experiences. For the last few months, they’ve been working together, exchanging instrumented JVM, logs, results and ideas… The exchanges are valuable for both the HotSpot JVM team and the OpenDS team, as together we’re really pushing Java and OpenDS to the limits, with a real case scenario.

For the OpenDS team, being able to tap in directly into the brains behind Java or ZFS, is a huge advantage.

You can find more details on Matt’s blog.

Technorati Tags: , , , , ,

OpenDS on Java.net front page…

Thanks to Marina Sum, our favorite Technical writer in the Identity management domain, and unfortunately now looking for new opportunities outside of Sun, OpenDS make it once again on the front page of Java.net.

OpenDS on Java.net front page.

Greatly appreciated, Marina.

Technorati Tags: , , , , ,

OpenDS on Java.net front page…

Thanks to Marina Sum, our favorite Technical writer in the Identity management domain, and unfortunately now looking for new opportunities outside of Sun, OpenDS make it once again on the front page of Java.net.

OpenDS on Java.net front page.

Greatly appreciated, Marina.

Technorati Tags: , , , , ,

Alive and Kicking…

Opends Logo Tag
The OpenDS project was launched almost 3 years ago, and while it took us some time to release a first stable release and we had a hiccup, the project has been constantly active.

An illustration of the activity can be found on Ohloh.net but unfortunately those statistics are not refreshed on a regular basis and the OpenDS ones haven’t been updated since August 2008.

Another illustration is this colorful visualization of the history of commits in the OpenDS source code repository, also known as CodeSwarm, that I’ve put together. Simply enjoy !


Technorati Tags: , , , , ,

LDAP Directory Services performance: optimize the filesystem cache !

Getting the best performance of an LDAP directory server is a difficult task as there are many parameters to take into account, especially with the hardware itself. The CPU clock matters for processing thousands of requests per second as fast as possible. The amount of memory controls how much caching can be done for optimization. The storage subsystem has has some importance on both read and write operations, both in term of throughput and response time. The network interfaces sets how fast to read and respond to client applications.

But the filesystem and how it is configured is also proven to be part of the equation.

Brad Diggs, aka “The Zone Manager” and Senior Directory Architect,has posted a long, detailed and extremely well written article on Filesystem cache optimization strategies, comparing UFS and ZFS, providing tuning tips for both of them.

To quote one of my co-worker:

“after I applied some of those changes, we went from 850 modifications per second to 1100 modifications per second, but more importantly the variation was drastically reduced, providing more constant performance”.

If you’re looking to optimize the performances of Sun Directory Server, or even OpenDS, this article is a must read, and make sure you keep a bookmark on it.

Technorati Tags: , , , , ,

OpenDS Tab Sweep March 17

I’m not doing regular tab sweep but there has been several interesting things said on or about OpenDS in the last few days.

Technorati Tags: , , ,

Learning LDAP in Universities and Engineering Schools…

In the last few weeks, I’ve been involved with giving lectures on LDAP to French students (in French).

On February 24th, I was at INSA Lyon for a 2 hours lecture introducing LDAP and Directory Services to an audience of approximately 120 students. The next day, Sylvain and 4 other engineers from the Sun Grenoble Engineering Center conducted 4 sessions of a 2 hours workshop on LDAP, Directory Services with OpenDS. Slides in French are available (and the English version as well).

On March 5th, invited by Julien Ponge, I was at ISIMA, the Engineering School from Clermont-Ferrand for a conference about LDAP and OpenDS. The talk was attended by about 30 students. Slides in French are here.

Technorati Tags: , , , , ,

OpenDS 1.3.0-Build001 is now available

Opends Logo TagWe have just uploaded OpenDS 1.3.0-build001, built from revision 5050 of our source tree, to our promoted builds folder.

OpenDS 1.3.0-build001 is the first promoted build from the trunk past the 1.2.0 stable release, and the first of a series leading to OpenDS 2.0 sometime in June.

There are many updates in this build, some internal code refactoring (like the ASN1 library and support), some performance improvements, some new features. Code for a new backend has been committed, but is not built by default. This backend provides a remote access to the NDB database used by MySQL Cluster.

Happy testing…

The direct link to download the core server is: http://www.opends.org/promoted-builds/1.3.0-build001/OpenDS-1.3.0-build001.zip

The direct link to download the DSML gateway is: http://www.opends.org/promoted-builds/1.3.0-build001/OpenDS-1.3.0-build001-DSML.war

We have also updated the archive that may be used to install OpenDS via Java Web Start. You may launch that using the URL http://www.opends.org/promoted-builds/1.3.0-build001/install/QuickSetup.jnlp, or visit https://www.opends.org/wiki/page/OverviewOfTheQuickSetupTool for more i

nformation.

Detailed information about this build is available at http://www.opends.org/promoted-builds/1.3.0-build001.

Major changes incorporated since OpenDS 1.2.0 include:

  • Revision 4714 – L10n localization of generated files.
  • Revision 4715 – Fix double extension loading when instance and install are in the same directory.
  • Revision 4717 (Issue #3621) – Ensure that the import-ldif command uses the correct default port (4444).
  • Revision 4718 – Upgrade the je.jar to verson 3.3.75.
  • Revision 4719 (Issue #3644) – Fix an issue that caused dsconfig to fail without an error message.
  • Revision 4722 – Change the TDES key size to use an effective key size of 112.
  • Revision 4723 & 4776 (Issues #3640 and 497) – Refactor the replication code to make it more generic and provide the assured replication feature.
  • Revision 4728 – Make the generic menu bar class public so that potential extensions of the control panel can use it.
  • Revision (Issue #3639) – Fix an issue that prevented a restore from being applied to the correct backend when more than one backend was defined.
  • Revision 4735 (Issue #3653) – Ensure that the status command displays the LDIF Connection Handler in its list of connection handlers.
  • Revision 4748 – Provide the ability to create a monitor provider with hierarchical naming, modify the Network Monitor provider names to include hierarchical naming, provide basic monitoring objects, add monitoring instrumentation for connection handlers, and add the ability to do a subtree search in the monitor backend.
  • Revision 4749 – Add two monitor objects.
  • Revision 4753 (Issue #3641) – Register service tags from SVR4 pkg installs.
  • Revision 4759 (Issue #274) – Provide support for recurring tasks.
  • Revision 4764 (Issue #3668) – Ensure that the Control Panel displays connection handler listen addresses correctly.
  • Revision 4765 – Improvements to the assured replication feature.
  • Revision 4768 (Issue #3657) – Correct a problem with the “Save” button in the “Manage Entries” panel.
  • Revision 4769 – Extend GenericDialog so that its extending classes can use a customized message for the title.
  • Revision 4770 (Issue #262) – Provide a plug-in for Collation/Internationalization.
  • Revision 4772 (Issue #3671) – Provide a configuration completed listener.
  • Revision 4773 (Issue #3645) – Generate aggregation constraints correctly.
  • Revision 4775 (Issue #3667) – Make dsconfig usage messages consistent.
  • Revision 4779 – Improvements to the assured replication feature.
  • Revision 4781 – Provide support for dynamic domain group id reconfiguration in replication servers.
  • Revision 4782 (Issue #3674) Provide support for backup and export in the tasks back end.
  • Revision 4783 – Allow for removal of backups in the schema back end.
  • Revision 4788 – Replace Latin1 characters with valid escaped UTF-8 characters in DNs/RDNs.
  • Revision 4791 – Implement support for click-through license approval in quicksetup.
  • Revision 4792 (Issue #3676) – Fix a problem that prevented ldapmodify from processing the ;binary transfer option.
  • Revision 4795 – Provide support for NULL back ends.
  • Revision 4800 (Issue #3694) – Fix the BER encoding/decoding for negative integers.
  • Revision 4803 (Issue #3689) – Fix an issue in which the Control Panel displayed the incorrect hostname.
  • Revision 4804 (Issue #3688) – Remove unexpected html tags in the output of the status command and provide support for connection handlers with multiple listen addresses.
  • Revision 4805 – Allow the extension of dsreplication userdata objects, extend the server descriptor used by the internal administrator, allow back ends to be disabled if the server is configured in manual mode.
  • Revision 4807 (Issue #3685) – Correct a Swing repainting problem in the control panel.
  • Revision 4808 (Issue #3695) – Improve the way in which the example plugin ant file handles message creation on Windows.
  • Revision 4809 (Issue #3640) – Improvements to the generic replication service.
  • Revisions 4810, 4811, 4817, 4818, 4819 & 4843 – Add support for client connection affinity.
  • Revision 4814 – Improve the license acceptance mechanism.
  • Revision 4815 – Enable OpenDS servers to load data from Directory Server Enterprise Edition servers.
  • Revision 4820 (Issue #3700) – Correct the handling of failure of a workflow element creation.
  • Revision 4822, 4842 – Fixes to the assured replication mechanism.
  • Revision 4823 (Issue #3699) – Correct the way in which the server handled the password Expired Control during a BIND operation, if the password had been reset.
  • Revision 4827 (Issue #3698) – Fix a problem that prevented changing the Directory Manager password with the Control Panel.
  • Revision 4829 – Allow import-ldif to load VLV indexes.
  • Revision 4830 (Issue #3701) – Correct the way in which setup manages back ends when replication involves multiple base-dns.
  • Revision 4831 (Issue #3709) – In the Control Panel, change the value of the “Backup Path” to the instance path (rather than the installation path)
  • Revision 4833 (Issue #2829) – Fix a problems that occurred when configuring and unconfiguring replication servers.
  • Revision 4835 (Issue #3710) – Fix a Control Panel error that occurred when creating a new base DN with automatically generated data.
  • Revision 4840 (Issue #3711) – Allow remote server debugging.
  • Revision 4844 – Reduce replication overhead.
  • Revision 4855 (Issue #3579) – Ensure that import-ldif countRejects works as expected.
  • Revision 4856 (Issue #3640) – Refactor replication code to make it more generic.
  • Revision 4858 & 4859 (Issue #3683) – Fix a problem that caused the replication conflict resolution code to assumes a conflict when replication replayed a DELETE on an entry with child entries.
  • Revision 4861 – Enable assured replication monitoring.
  • Revision 4862 (Issue #3716) – Fix a problem that caused start-ds.bat to use the wrong environment variable for passing arguments.
  • Revision 4863 (Issue #3717) – Allow command line output and error stream to be changed.
  • Revision 4870 & 4902 (Issue #3724) – Instead of using a hardcoded trust manager provider and algorithm, takes the default algorithm of the JVM.
  • Revision 4872 (Issue #3723) – Fix the ACI SSF bind rule != operator.
  • Revision 4874 (Issue #3718) – Correct a problem that caused the -A, –typesOnly option to be ignored by ldapsearch.
  • Revision 4887 (Issue #3131) – Fix a problem that caused upgrades using the webinstaller to hang on Windows.
  • Revision 4896 (Issue #3731) – Remove the status-panel command (which has been replaced by control-panel.
  • Revision 4898 (Issue #3733) – When performing a search on the root DSE to retrieve the list of namingContexts, display only the public naming contexts visible through the current network group.
  • Revision 4905 (Issue #3736) – Correct a problem that prevented replication dynamic purge delay changes from being taken into account.
  • Revision 4909 (Issue #3750) – Improve the behaviour when forcing a password change after admin reset.
  • Revision 4912 – Extend the directory server so that other tools launching it can impose their own usage message.
  • Revision 4921 – Allow overwriting classes to specify whether the schema should be read.
  • Revision 4922 (Issue #3726) – Fix a problem that prevented the RealAttributesOnly Control from working when the types-only search option was enabled.
  • Revision 4923 – Add 508 compliance to the Browse Schema panels on the Control Panel.
  • Revision 4925 – Update the ServiceTag data configuration with an optional configuration directory.
  • Revision 4926 & 4928 (Issue #3760 & 3761) – Fix a problem that caused dsconfig to exit abruptly when creating a component with a missing parent or when creating a component with the same name.
  • Revision 4931 (Issues #3446 & 3726) – Introduce comprehensive unit tests for checking attribute filtering in search operations, add improvements to the virtual attribute provider API, add improvements to virtual attribute processing during Entry duplication.
  • Revision 4932 (Issues #3682 & 3643) – Addition of localized resource files with new translations.
  • Revision 4937 (Issue #3561) – Fix an issue that prevented aliased attributes from being returned properly.
  • Revision 4941 (Issue #3763) – Provide a dsconfig error message if a type of object does not exist.
  • Revision 4942 – Fix a problem that prevented entry locks from being released.
  • Revision 4944 – Update the SVR4 factory to avoid conflict with the IPS factory.
  • Revision 4946 – Provide support for collation indexing.
  • Revision 4949 – Fix a problem with IPv4 wild card pattern matching that prevented address masks of the form “*.*.*.*” from ever matching an IPv4 address.
  • Revision 4950 (Issue #3734) – Make network group policies extensible.
  • Revision 4956, 4957 & 4961 – ASN1 refactoring.
  • Revision 4958 – Make it possible for users to configure the Control Panel refresh period.
  • Revision 4962 (Issue #3391) – Fix a problem that prevented custom DIT Structure Rules from being added to 99-user.ldif.
  • Revision 4963 (Issue #3606) – Fix a problem that prevented the isMemberOf attribute from working for dynamic groups.
  • Revision 4964 – Add a user interface to display global monitoring information and connection handler monitoring information.
  • Revision 4969 (Issue #3775) – Fix an intermittent unit test failure in the NetworkGroupTest and add support for finalizing the NetworkGroupConfigManager.
  • Revision 4972 – Add the displayCommand and commandFilePath options to the dsreplication command. Also, fix an issue that prevented some passwords passed in the command-line as file arguments from being taken into account in interactive mode.
  • Revision 4981 – Add a check for a null SASL Context and fix an error message in the EXTERNAL Digest Handler.
  • Revision 4986 – First phase of support for an NDB backend.
  • Revision 4991 (Issue #3795) – Fix a problem that caused TLS to fail when adding or modifying a large attribute.
  • Revision 4993 (Issue #3797) – Ensure that the directory server logs it’s instance path at startup.
  • Revision 4998 (Issue #3774) – Fix a problem that prevente the sort control from working with collation matching rules.
  • Revision 4999 (Issue #3801) – If a connection handler has no address defined in its configuration, only show the port of the connection handler, rather than a fictitiuos address.
  • Revision 5004 (Issue #3805) – Support for SASL Connection Security (Phase2).
  • Revision 5006 (Issue #3806) – Fix a problem that caused an ldapsearch operation on the rootDSE to return error 255 if no back end was defined.
  • Revision 5008 (Issue #3800) – Redesign the Monitoring General Information panel to handle the display of a large number of operations.
  • Revision 5009 (Issue #3806) – Prevent schema elements in 06-compat.ldif from being deleted by a user.
  • Revision 5010 (Issue #3803) – Correct ASN.1 encoding of VLVResponseControl so it sends the result code as a BER Enumerated instead of Integer.
  • Revision 5011 (Issue #3809) – Add a flush() call to the ASN1Writer to make sure that all bytes are sent out.
  • Revision 5017 (Issue #3812) – Display a warning if the user provides the wrong replication port for an existing replication server.
  • Revision 5018 (Issue #3804) – Improve replication monitoring.
  • Revision 5023 (Issue #3815) – Declare NS password expire and expiring in the SupportControl in the RootDSE.
  • Revision 5024 (Issue #3820) – Fix an issue that prevented the removal of spaces at the end of string with Non-ASCII characters.
  • Revision 5025 (Issues #3687 & 3690) – Fix a problem that caused incorrect SNMP values to be displayed.
  • Revision 5027 (Issue #3817) – Fix a problem that caused a the configuration to break if a 2nd workflow with cn=config baseDn can break the configuration.
  • Revision 5029 & 5030 (Issue #3802) – Fix incorrect script launcher return codes.
  • Revision 5031 & 5035 (Issue #3826) – ix a problem that prevented ldapsearch from prompting for a bind password if the option -w was not provided.
  • Revision 5032 (Issue #3798) – Fix a problem that prevented the server from using more than 50% of machine memory.
  • Revision 5033 (Issues #3808 & 3810) – Fix the hasSubordinates attribute under cn=monitor and prevent a Parent DN entry from being returned when using a child entry as the search base DN.
  • Revision 5036 (Issue #3765) – Correct the way in which export-ldif handles relative paths.
  • Revision 5038 (Issue #3834) – Fix a problem that caused an exception when dsconfig was used to configure a Network Group QOS Policy in interactive mode.
  • Revision 5040 (Issue #3840) – Fix a problem in the license file that broke the Java Web Start installer.
  • Revision 5042 (Issue #3849) – Allow read-only properties to be modified at component creation time.
  • Revision 5043 (Issue #3846) – Provide routines in the WorkflowElement class to retrieve child workflow elements.
  • Revision 5044 (Issue #3841) – Fix performance degradations observed when using LDAPWriter.
  • Revision 5045 (Issue #3852) – Fix a problem that caused dsconfig to exit when parent component did not exist, if run in interactive mode.
  • Revision 5046 (Issue #3844) – Ensure that replication changes are not lost when ReplicationDomain.publish is called by several threads.
  • Revision 5050 (Issue #3845) – Fix an IllegalStateException that occurred during Schema Backend initialization.

Technorati Tags: , , , , ,