Apache Directory Studio 2.0.0-M5 released
The Apache Directory Team is pleased to announce the release of Apache Directory Studio 2.0.0-M5, the fifth milestone release of the version 2.0 of its Eclipse based LDAP Browser and Directory client. You can download Apache Directory Studio 2.0.0-M5 as a standalone RCP application for Mac OS X, Linux and Windows at: http://directory.apache.org/studio You can also install it directly in Eclipse using this update site: http://directory.apache.org/studio/update/2.x/ Here are the release notes for Apache Directory Studio 2.0.0-M5 (combined with version 2.0.0-M4, which was not announced): Bug DIRSTUDIO-775 - Display issues in Image Editor DIRSTUDIO-795 - Unable to delete multiple schema elements (attribute type, object class or schema) DIRSTUDIO-796 - Unable to open multiple schema elements (attribute type, object class or schema) DIRSTUDIO-799 - Unable to move object with Apache LDAP API DIRSTUDIO-802 - Confusion between ISO-8859-1 and UTF-8 in the Encode/Decode dialog DIRSTUDIO-808 - Update existing entries checkbox in LDIF Import wizard fails to work with the Apache Directory LDAP API DIRSTUDIO-810 - Fullscreen plugin is /not/ under the Apache license DIRSTUDIO-812 - Error while performing search DIRSTUDIO-822 - Typo in one of the default indexed attributes when creating a new partition in the ApacheDS Configuration Editor v2 DIRSTUDIO-823 - Integer Value Editor only selects values of Java Integer magnitude DIRSTUDIO-827 - Quick Search is not displayed when folding is activated DIRSTUDIO-829 - NPE when trying to add a 'subtreeSpecification' value DIRSTUDIO-833 - NPE in ACI Item Editor when adding AttributeType permission DIRSTUDIO-834 - Unable to edit subtreeSpecification DIRSTUDIO-835 - Display issues in the Password Editor on OS X DIRSTUDIO-840 - Help system is not working DIRSTUDIO-850 - The Remove button for mandatory ATs in the OC Editor does nothing DIRSTUDIO-858 - The Entry Editor's Outline view should be unavailable when the selection isn't an entry or a bookmark DIRSTUDIO-864 - Error message appears: ERR_04269 ATTRIBUTE_TYPE for OID ads-replenabled does not exist! when trying to open configuration DIRSTUDIO-867 - References of old projects and packages name 'org.apache.directory.shared' still present in the code Improvement DIRSTUDIO-657 - Add options to output the resulting LDIF of a batch operation to a file or to the clipboard DIRSTUDIO-793 - Batch Operation define modification slowdown, needs scrollbar DIRSTUDIO-797 - Two different 'HistoryUtils' classes should be merged into a single one in 'common.ui' plugin DIRSTUDIO-809 - Improve the behavior of the Execute LDIF action of the LDIF Editor DIRSTUDIO-813 - Add default value editors for eDirectory DIRSTUDIO-828 - The Quick Search context menu item could reuse the currently selected entry in the Browser view as search base DIRSTUDIO-838 - Add support for configuring the context entry of a partition in the ApacheDS 2.0 Configuration Editor DIRSTUDIO-841 - When creating a connection from an existing ApacheDS 2.0 server, the Open Configuration item is not available DIRSTUDIO-851 - Add a hint in the Connection Properties dialog about Certifcate Validation with a link to the corresponding preference page DIRSTUDIO-852 - Display issues in the Certificate Validation preference page on OS X New Feature DIRSTUDIO-804 - Interpret Active Directory Timestamps DIRSTUDIO-806 - Editing Multiple Directory Objects at once DIRSTUDIO-843 - There is no place we can configure the KeyStore to use while configuring an ApacheDS server Task DIRSTUDIO-736 - Implement the Execute Online button of the BatchOperationWizard DIRSTUDIO-791 - Update supportedControl and supportedExtension descriptions DIRSTUDIO-811 - Review and remove any source file under Eclipse Public License (EPL) v 1.0 DIRSTUDIO-816 - Update OIDs to Descriptions properties file DIRSTUDIO-839 - Update Eclipse dependencies to version 3.8.1 The Apache Directory Team
[jira] [Commented] (DIRSTUDIO-874) Remove all ApacheDS libraries plugins
[ https://issues.apache.org/jira/browse/DIRSTUDIO-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13576631#comment-13576631 ] Francis ANDRE commented on DIRSTUDIO-874: - Hi From what I understand from the ApacheDS Studio structures, directories and installation guide, the bundles are produced from the librairies by mvn clean install studio:eclipse . So why do you want to remove them? Remove all ApacheDS libraries plugins - Key: DIRSTUDIO-874 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-874 Project: Directory Studio Issue Type: Task Reporter: Pierre-Arnaud Marcelot Assignee: Pierre-Arnaud Marcelot Fix For: 2.0.0-M6, 2.0.0 ApacheDS libraries plugins are completely unnecessary now as they are all available as bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DIRSTUDIO-874) Remove all ApacheDS libraries plugins
[ https://issues.apache.org/jira/browse/DIRSTUDIO-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13576636#comment-13576636 ] Pierre-Arnaud Marcelot commented on DIRSTUDIO-874: -- Hi Francis, These 'library' projects were added to Apache Directory Studio at a time where ApacheDS modules were not OSGI bundles but simple jar files. That's the case now, so we can get rid of this hacky bundle refactoring. The idea is not to remove them from the distribution but to avoid a useless repackaging to make them OSGI bundles now that they are already plain OSGI bundles. We can now safely use them as is. Hope this helps. Remove all ApacheDS libraries plugins - Key: DIRSTUDIO-874 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-874 Project: Directory Studio Issue Type: Task Reporter: Pierre-Arnaud Marcelot Assignee: Pierre-Arnaud Marcelot Fix For: 2.0.0-M6, 2.0.0 ApacheDS libraries plugins are completely unnecessary now as they are all available as bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (DIRKRB-87) When we configure a wrong EncryptionType, the server does not start
Emmanuel Lecharny created DIRKRB-87: --- Summary: When we configure a wrong EncryptionType, the server does not start Key: DIRKRB-87 URL: https://issues.apache.org/jira/browse/DIRKRB-87 Project: Directory Kerberos Issue Type: Bug Reporter: Emmanuel Lecharny Assignee: Emmanuel Lecharny When we add a wrong encryptionType in the configuration, the server does not start anymore : [15:22:59] ERROR [org.apache.directory.server.wrapper.ApacheDsTanukiWrapper] - Failed to start the service. java.lang.IllegalArgumentException: Unknown algorithm name for the encryption type UNKNOWN (-1) at org.apache.directory.shared.kerberos.KerberosUtils.getAlgoNameFromEncType(KerberosUtils.java:388) at org.apache.directory.shared.kerberos.KerberosUtils.orderEtypesByStrength(KerberosUtils.java:400) at org.apache.directory.server.kerberos.KerberosConfig.setEncryptionTypes(KerberosConfig.java:215) at org.apache.directory.server.config.builder.ServiceBuilder.createKdcServer(ServiceBuilder.java:682) at org.apache.directory.server.ApacheDsService.startKerberos(ApacheDsService.java:469) at org.apache.directory.server.ApacheDsService.start(ApacheDsService.java:197) at org.apache.directory.server.wrapper.ApacheDsTanukiWrapper.start(ApacheDsTanukiWrapper.java:72) at org.tanukisoftware.wrapper.WrapperManager$12.run(WrapperManager.java:2788) Here is the wrong value in ads-serverid=kerberosserver,ou=servers,ads... : ads-krbencryptiontypes: aeswrongalgo -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (DIRKRB-87) When we configure a wrong EncryptionType, the server does not start
[ https://issues.apache.org/jira/browse/DIRKRB-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kiran Ayyagari resolved DIRKRB-87. -- Resolution: Fixed Assignee: Kiran Ayyagari (was: Emmanuel Lecharny) Fixed here http://svn.apache.org/r1445178 When we configure a wrong EncryptionType, the server does not start --- Key: DIRKRB-87 URL: https://issues.apache.org/jira/browse/DIRKRB-87 Project: Directory Kerberos Issue Type: Bug Reporter: Emmanuel Lecharny Assignee: Kiran Ayyagari When we add a wrong encryptionType in the configuration, the server does not start anymore : [15:22:59] ERROR [org.apache.directory.server.wrapper.ApacheDsTanukiWrapper] - Failed to start the service. java.lang.IllegalArgumentException: Unknown algorithm name for the encryption type UNKNOWN (-1) at org.apache.directory.shared.kerberos.KerberosUtils.getAlgoNameFromEncType(KerberosUtils.java:388) at org.apache.directory.shared.kerberos.KerberosUtils.orderEtypesByStrength(KerberosUtils.java:400) at org.apache.directory.server.kerberos.KerberosConfig.setEncryptionTypes(KerberosConfig.java:215) at org.apache.directory.server.config.builder.ServiceBuilder.createKdcServer(ServiceBuilder.java:682) at org.apache.directory.server.ApacheDsService.startKerberos(ApacheDsService.java:469) at org.apache.directory.server.ApacheDsService.start(ApacheDsService.java:197) at org.apache.directory.server.wrapper.ApacheDsTanukiWrapper.start(ApacheDsTanukiWrapper.java:72) at org.tanukisoftware.wrapper.WrapperManager$12.run(WrapperManager.java:2788) Here is the wrong value in ads-serverid=kerberosserver,ou=servers,ads... : ads-krbencryptiontypes: aeswrongalgo -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DIRSTUDIO-874) Remove all ApacheDS libraries plugins from trunk in '/libraries'
[ https://issues.apache.org/jira/browse/DIRSTUDIO-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot updated DIRSTUDIO-874: - Summary: Remove all ApacheDS libraries plugins from trunk in '/libraries' (was: Remove all ApacheDS libraries plugins) Remove all ApacheDS libraries plugins from trunk in '/libraries' Key: DIRSTUDIO-874 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-874 Project: Directory Studio Issue Type: Task Reporter: Pierre-Arnaud Marcelot Assignee: Pierre-Arnaud Marcelot Fix For: 2.0.0-M6, 2.0.0 ApacheDS libraries plugins are completely unnecessary now as they are all available as bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DIRSTUDIO-874) Remove all ApacheDS and Apache Mina libraries plugins from trunk in '/libraries'
[ https://issues.apache.org/jira/browse/DIRSTUDIO-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pierre-Arnaud Marcelot updated DIRSTUDIO-874: - Summary: Remove all ApacheDS and Apache Mina libraries plugins from trunk in '/libraries' (was: Remove all ApacheDS libraries plugins from trunk in '/libraries') Remove all ApacheDS and Apache Mina libraries plugins from trunk in '/libraries' Key: DIRSTUDIO-874 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-874 Project: Directory Studio Issue Type: Task Reporter: Pierre-Arnaud Marcelot Assignee: Pierre-Arnaud Marcelot Fix For: 2.0.0-M6, 2.0.0 ApacheDS libraries plugins are completely unnecessary now as they are all available as bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (DIRSTUDIO-874) Remove all ApacheDS and Apache Mina libraries plugins from trunk in '/libraries'
[ https://issues.apache.org/jira/browse/DIRSTUDIO-874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13576669#comment-13576669 ] Francis ANDRE commented on DIRSTUDIO-874: - Hi Pierre-Arnaud Ok I got the point. Thanks for the clarification. Remove all ApacheDS and Apache Mina libraries plugins from trunk in '/libraries' Key: DIRSTUDIO-874 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-874 Project: Directory Studio Issue Type: Task Reporter: Pierre-Arnaud Marcelot Assignee: Pierre-Arnaud Marcelot Fix For: 2.0.0-M6, 2.0.0 ApacheDS libraries plugins are completely unnecessary now as they are all available as bundles. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (DIRSERVER-1797) The AdministrativeRole AT is not indexed, leadings to huge delay when starting the server
Emmanuel Lecharny created DIRSERVER-1797: Summary: The AdministrativeRole AT is not indexed, leadings to huge delay when starting the server Key: DIRSERVER-1797 URL: https://issues.apache.org/jira/browse/DIRSERVER-1797 Project: Directory ApacheDS Issue Type: Bug Affects Versions: 2.0.0-M10 Reporter: Emmanuel Lecharny Priority: Blocker Fix For: 2.0.0-M11 As the AdministrativeRole AT is not indexed by default, we always do a full scan searching for the associated entries when the server is started, which takes a hell of a time. This is because the AdministrativeIntnerceptor is activated, and the init() phase does a search of all the AP in the tree. We have to add this AT in the list of system index -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (DIRSERVER-1798) The AdministrativePoint interceptor is always activated, even if it's not part of the config
Emmanuel Lecharny created DIRSERVER-1798: Summary: The AdministrativePoint interceptor is always activated, even if it's not part of the config Key: DIRSERVER-1798 URL: https://issues.apache.org/jira/browse/DIRSERVER-1798 Project: Directory ApacheDS Issue Type: Bug Affects Versions: 2.0.0-M10 Reporter: Emmanuel Lecharny Fix For: 2.0.0-M11 Even if it's not declared in the configuration file, this interceptor is started by default. That means we don't really take care of the configuration, it does not overwrite the DefaultDirectoryServer.setDefaultInterceptorConfigurations() config, which is weird. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (DIRSTUDIO-875) Can't create custom Object Class
Daniel Jorgensen created DIRSTUDIO-875: -- Summary: Can't create custom Object Class Key: DIRSTUDIO-875 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-875 Project: Directory Studio Issue Type: Bug Components: studio-ldifeditor Environment: ADS Version: 2.0.0.v20130125, Server: ApacheDS 2.0.0 Reporter: Daniel Jorgensen Priority: Blocker I'm getting a ERR_251_PARENT_NOT_FOUND exception when I try to import a new LDIF containing a new Object Class. I've tried following the steps listed here https://issues.apache.org/jira/browse/DIRSTUDIO-831 The problem occurs when importing the new LDIF file. It can't find my new class in the tree. But shouldn't it be creating it? I'm relatively new to LDAP, so it's quite possible that I'm missing something which could be perceived as obvious to someone with more experience. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Are all the System index really fed ?
H, I'm probably a bit too deep into the code atm, but it seems to me that the system index are never updated, except ObjectClass, Rdn, entryCSN and alias indexes. The entryUUID and AdministrativeRole indexes are never updated, as far as I can say. Is this just me ? -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
Re: Are all the System index really fed ?
Le 2/12/13 8:58 PM, Emmanuel Lécharny a écrit : H, I'm probably a bit too deep into the code atm, but it seems to me that the system index are never updated, except ObjectClass, Rdn, entryCSN and alias indexes. The entryUUID and AdministrativeRole indexes are never updated, as far as I can say. Is this just me ? It's just me :) The EntrtyUUID is not anymore necessary, as we use the MasterTable for that (each entry is referenced by its entryUUID in this table. If we need to retrieve an entry from its entryUUID, we just have to read it). The AdministratveRole index is not fed, though. It's a bit problematic, because it has to be a System index, while it was considered as a user index before, forcing the user creating a new partition to explicitely dclare it in its configuration file, something really not convenient. That requires many modification in teh AbstratBtreePartition code. -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
[jira] [Created] (DIRSERVER-1799) When deleting values from an existing entry, the presence index might get out of date
Emmanuel Lecharny created DIRSERVER-1799:
Summary: When deleting values from an existing entry, the presence
index might get out of date
Key: DIRSERVER-1799
URL: https://issues.apache.org/jira/browse/DIRSERVER-1799
Project: Directory ApacheDS
Issue Type: Bug
Affects Versions: 2.0.0-M10
Reporter: Emmanuel Lecharny
Priority: Critical
Fix For: 2.0.0-M11
We use the reverse index to detect if an AT is not anymore present in an entry
after a modification ::
/*
* If no attribute values exist for this entryId in the index then
* we remove the presence index entry for the removed attribute.
*/
if ( null == index.reverseLookup( id ) )
{
presenceIdx.drop( modsOid, id );
}
If the AT index does not have a reverse index, this operation will do nothing,
and the presence index will select entries which are not anymore useful.
We should instead check if the Attribute is still existng after the
modification, and if not, remove it from the presence index without checking
into it.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
about groovy ldap jar
Hi I ve tried downloading groovy-ldap.zip but it is inaccessible. Can you please fix it or send me the zip file via e-mail. Regards
Re: about groovy ldap jar
Le 2/13/13 7:41 AM, Onur Kulaat a écrit : Hi I ve tried downloading groovy-ldap.zip but it is inaccessible. Can you please fix it or send me the zip file via e-mail. Regards Works fine for me, since I fixed the link 2 days ago. Have you read my answer to your previous mail ? -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
