[jira] [Resolved] (DIRAPI-150) A search done with a wrong baseDN does not return a NO_SUCH_ERROR
[ https://issues.apache.org/jira/browse/DIRAPI-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Lecharny resolved DIRAPI-150. -- Resolution: Not A Problem Yes, this is on purpose. When doing a lookup() or a search(), if the base DN does not exist, you will simply get no result. Is this a problem for you ? A search done with a wrong baseDN does not return a NO_SUCH_ERROR - Key: DIRAPI-150 URL: https://issues.apache.org/jira/browse/DIRAPI-150 Project: Directory Client API Issue Type: Bug Affects Versions: 1.0.0-M18 Reporter: Emmanuel Lecharny Priority: Blocker Fix For: 1.0.0-RC1 When we do a search with a non existing baseDN, we get back an empty cursor instead of getting an LdapNoSuchObjectException. -- 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] (DIRSERVER-1489) Provide access to remote connection info
[ https://issues.apache.org/jira/browse/DIRSERVER-1489?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13716176#comment-13716176 ] Kiran Ayyagari commented on DIRSERVER-1489: --- Added another fix to provide the connection information when an operation was performed anonymously, see http://svn.apache.org/r1505919 Provide access to remote connection info Key: DIRSERVER-1489 URL: https://issues.apache.org/jira/browse/DIRSERVER-1489 Project: Directory ApacheDS Issue Type: Improvement Affects Versions: 1.5.5 Reporter: Matt Doran Fix For: 2.0.0-M13 Attachments: connection-info-1.5.5.patch, connection-info-1.5.5-v2.patch I'm developing a custom partition and custom authentication handler to plug into ApacheDS, and need to know the connection details of the client performing the requests.A reason why this might be useful it to be able to log the source of invalid authentication requests. The CoreSession object has a getClientAddress() method, however it always returns null. The CoreSession object is accessible from the places where it would be useful (i.e. via the context objects passed into the Partition methods ... and also in the AuthenticationInterceptor.) Upon further investigation it looks like the implementation in DefaultCoreSession is hard-coded to return null. :( It also appears that the services main CoreSession object is reused alot (e.g. in the authentication interceptor we use the same session object no matter who the caller is). I was interested in putting in a short-term patch to work-around this issue while a longer term solution was considered. But I couldn't find anything obvious. I'd think it would make sense to stuff the client address into the session somewhere up in one of the protocol handlers (e.g. LdapRequestHandler.handleMessage) ... but there currently isn't anywhere to put this info. Any ideas on a short-term (even if hacky) way to achieve this? (raising as requested by Emmanuel Lecharany on user's list) -- 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-1872) The JournalInterceptor is not present in the configuration
Emmanuel Lecharny created DIRSERVER-1872: Summary: The JournalInterceptor is not present in the configuration Key: DIRSERVER-1872 URL: https://issues.apache.org/jira/browse/DIRSERVER-1872 Project: Directory ApacheDS Issue Type: Bug Affects Versions: 2.0.0-M14 Reporter: Emmanuel Lecharny Fix For: 2.0.0-RC1 For some strange reason, it was never added... -- 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] (DIRSERVER-1872) The JournalInterceptor is not present in the configuration
[ https://issues.apache.org/jira/browse/DIRSERVER-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Emmanuel Lecharny resolved DIRSERVER-1872. -- Resolution: Fixed Fixed with http://svn.apache.org/r1505919 The JournalInterceptor is not present in the configuration --- Key: DIRSERVER-1872 URL: https://issues.apache.org/jira/browse/DIRSERVER-1872 Project: Directory ApacheDS Issue Type: Bug Affects Versions: 2.0.0-M14 Reporter: Emmanuel Lecharny Fix For: 2.0.0-RC1 For some strange reason, it was never added... -- 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] [Comment Edited] (DIRSERVER-1872) The JournalInterceptor is not present in the configuration
[ https://issues.apache.org/jira/browse/DIRSERVER-1872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13716200#comment-13716200 ] Emmanuel Lecharny edited comment on DIRSERVER-1872 at 7/23/13 7:27 AM: --- Fixed with http://svn.apache.org/r1505923 was (Author: elecharny): Fixed with http://svn.apache.org/r1505919 The JournalInterceptor is not present in the configuration --- Key: DIRSERVER-1872 URL: https://issues.apache.org/jira/browse/DIRSERVER-1872 Project: Directory ApacheDS Issue Type: Bug Affects Versions: 2.0.0-M14 Reporter: Emmanuel Lecharny Fix For: 2.0.0-RC1 For some strange reason, it was never added... -- 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
Re: Failure when creating a new entity using a custom object class that includes a SUP attribute
Hi Emmanuel,
Thanks, that's much better and far more readable. :)
This is an interesting issue.
I could play with the code you provided and I suspect an issue in the schema
handling. Either something not enabled correctly or something deeper in the
server.
Investigating...
Regards,
Pierre-Arnaud
On 22 juil. 2013, at 19:43, Emmanuel GUITON emmanuel.gui...@intrinsec.com
wrote:
Hi,
Very sorry for the inconvenience, I hope this time will be better :
In an embbeded Apache DS instance, I am trying to add an entity using a
custom object class but it fails. Here is the scenario :
First, I set up a default Apache DS instance, with the schema defined in
(maven) :
dependency
groupIdorg.apache.directory.api/groupId
artifactIdapi-ldap-schema-data/artifactId
version1.0.0-M19/version
/dependency
Then, I add (programatically) my custom type using the JNDI. This type
extends the 'organization' object class. Browsing the schema with a GUI tool
(JXplorer), I ensure my custom object class was successfully added.
After that, I add a new entity (using the JNDI once again or using the GUI
tool) and the following exception is thrown :
javax.naming.directory.SchemaViolationException: [LDAP: error code 65 -
OBJECT_CLASS_VIOLATION: failed for MessageType : ADD_REQUEST
Message ID : 5
Add Request :
Entry
dn[n]: o=Test,dc=company,dc=com
objectClass: orgExtended
o: Test
OpaqueControl Control
Type OID: '2.16.840.1.113730.3.4.2'
Criticality : 'false'
'
: ERR_277 Attribute o not declared in objectClasses of entry
o=Test,dc=company,dc=com]; remaining name 'o=Test,dc=company,dc=com'
However, I did specify the value of the 'o' attribute, which is defined in
the parent object class (organization).
I stress that the object class definition includes a SUP attribute. I have
other custom object classes without SUP attribute. I can successfully create
new entities using these other object classes.
Is this a bug or am I missing something ?
Hereafter, you can find a complete (client side) code snippet to repeat this
behaviour.
Thanks for any help,
- emmanuel
package com.company.directory.client;
import java.util.Hashtable;
import javax.naming.Context;
import javax.naming.Name;
import javax.naming.NamingException;
import javax.naming.directory.Attributes;
import javax.naming.directory.BasicAttributes;
import javax.naming.directory.DirContext;
import javax.naming.directory.InitialDirContext;
import javax.naming.ldap.LdapName;
public class ApacheDsTest
{
public static void main(final String[] args)
{
try
{
// Init connection to the LDAP server
final HashtableString, String env = new
HashtableString, String();
env.put(Context.INITIAL_CONTEXT_FACTORY,
com.sun.jndi.ldap.LdapCtxFactory);
env.put(Context.PROVIDER_URL, TestUtils.PROVIDER_URL);
env.put(Context.SECURITY_AUTHENTICATION, simple);
env.put(java.naming.ldap.derefAliases, always);
env.put(Context.SECURITY_PRINCIPAL,
uid=admin,ou=system);
env.put(Context.SECURITY_CREDENTIALS, secret);
final DirContext context = new InitialDirContext(env);
// Add new objectClass, extends organization
final Attributes attrs = new BasicAttributes();
attrs.put(NUMERICOID, 1.3.6.1.4.1.8654.4.1);
attrs.put(NAME, orgExtended);
attrs.put(DESC, Extension of the organization
object class);
attrs.put(SUP, organization);
attrs.put(STRUCTURAL, TRUE);
final DirContext schemaContext = context.getSchema();
schemaContext.createSubcontext(ClassDefinition/orgExtended, attrs);
// dn: o=Test,dc=company,dc=com, objectClass:
orgExtended, o: Test
final Name name = new
LdapName(o=Test,dc=company,dc=com);
final Attributes attributes=new BasicAttributes();
attributes.put(objectClass, orgExtended);
attributes.put(o, Test);
context.createSubcontext(name, attributes);
}
catch (final NamingException exception)
{
System.err.println(exception);
}
}
}
Emmanuel GUITON
Ingénieur Développement
Fixe : +33 1 70 92 84 16 l Standard : +33 1 41 91 77 77
215, Avenue Georges Clemenceau l 92024 Nanterre
http://www.intrinsec.com/
http://www.intrinsec.com/
-Message d'origine-
De :
After adding new m-may attribute to a custom class in a schema, can't then add the attribute to an entry
Hi,
I'm having odd issues with adding a new m-may attribute to a custom
metaObjectClass in our schema. We created a custom class in the initial
release of the software with the following ldif:
dn: m-oid=1.3.6.1.4.1.26156.30.0.0.1.12, ou=objectClasses, cn=conneqt-config,
ou=schema
objectclass: metaObjectClass
objectclass: metaTop
objectclass: top
m-oid: 1.3.6.1.4.1.26156.30.0.0.1.12
m-name: adapterMailbox
m-supObjectClass: top
m-must: email
m-must: smtpHost
m-must: smtpPort
m-must: userPassword
Further changes then required the addition of an optional enabled/disabled
flag, so the following update ldif was created:
dn: m-oid=1.3.6.1.4.1.26156.30.0.0.0.1, ou=attributeTypes, cn=conneqt-config,
ou=schema
objectclass: metaAttributeType
objectclass: metaTop
objectclass: top
m-oid: 1.3.6.1.4.1.26156.30.0.0.0.1
m-name: isActiveFlag
m-description: A boolean flag to indicate if an entry is active or not
m-equality: caseIgnoreMatch
m-ordering: booleanMatch
m-syntax: 1.3.6.1.4.1.1466.115.121.1.7
m-length: 1
m-singleValue: TRUE
dn: m-oid=1.3.6.1.4.1.26156.30.0.0.1.12, ou=objectClasses, cn=conneqt-config,
ou=schema
changetype: modify
add: m-may
m-may: isActiveFlag
Now the problems I have are two-fold: firstly, when I try to add the
isActiveFlag attribute to an entry through Apache Directory Studio, it gives a
warning saying the attribute type is not allowed. Whilst I can click through
this, the second problem is that when I try to add entries programmatically:
var name = string.Format(email={0}, emailAddress);
var entry = container.Children.Add(name, adapterMailbox);
entry.Properties[userPassword].Value = password;
entry.Properties[smtpHost].Value = smtpHost;
entry.Properties[smtpPort].Value = smtpPort;
entry.Properties[isActiveFlag].Value = isActiveFlag;
entry.CommitChanges();
It is throwing a DirectoryServicesCOMException with message The requested
operation did not satisfy one or more constraints associated with the class of
the object.
Anyone able to shed any light on what might be going on?
Cheers
Matthew Goudge
Developer
[Quicksilva]http://www.qxlva.com/
Quicksilva Systems Integration Solutions | www.qxlva.comhttp://www.qxlva.com/
Tel: 01249 751 000 | matthew.gou...@qxlva.commailto:matthew.gou...@qxlva.com
[Twitter]http://twitter.com/QxlvaHealth[LinkedIn]http://www.linkedin.com/company/quicksilva[MerQury]http://www.qxlva.com/MerQury/
__
The Company gives no warranty as to the accuracy or completeness of electronic
mail messages sent over the Internet and accepts no responsibility for changes
made after it was sent. Any opinion expressed in this email may be personal to
the author, may not necessarily reflect the opinions of the Company or its
affiliates and may be subject to change without notice.
The information contained in this communication is confidential and/or
proprietary business or technical data. If you are not the intended recipient,
you are hereby notified that any dissemination, copying or distribution of this
communication, or the taking of any action in reliance on the contents of this
communication, is strictly prohibited. If you have received this communication
in error, please immediately notify us electronically by return message, and
delete or destroy all copies of this communication.
Quicksilva Limited, Reg No 3860799, Incorporated at Companies House, Cardiff.
Registered Office: Langley Gate, Swindon Road, Chippenham, Wiltshire, SN15 5SE.
Vat Reg No 762 8082 16.
__
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
__inline: image001.gifinline: image002.gifinline: image003.gifinline: image004.gif
Re: After adding new m-may attribute to a custom class in a schema, can't then add the attribute to an entry
Hi Matthew,
Did you restart the server ?
Additions don't need a server-restart and are handled on the fly.
Modifications on an existing schema element, though, are not very recommended
(especially if you already have data using this schema element) and I'm not
really sure they are handled on the fly as well.
On the Studio side, if you've modified the schema without closing/reopening the
connection or manually reloading the schema (in the connection's properties or
in the Schema view), the modification won't be reflected, hence the message you
got.
A simple close/reopen of the connection should fix that.
Regards
Pierre-Arnaud
On 23 juil. 2013, at 16:39, Matthew Goudge matthew.gou...@qxlva.com wrote:
Hi,
I’m having odd issues with adding a new m-may attribute to a custom
metaObjectClass in our schema. We created a custom class in the initial
release of the software with the following ldif:
dn: m-oid=1.3.6.1.4.1.26156.30.0.0.1.12, ou=objectClasses, cn=conneqt-config,
ou=schema
objectclass: metaObjectClass
objectclass: metaTop
objectclass: top
m-oid: 1.3.6.1.4.1.26156.30.0.0.1.12
m-name: adapterMailbox
m-supObjectClass: top
m-must: email
m-must: smtpHost
m-must: smtpPort
m-must: userPassword
Further changes then required the addition of an optional enabled/disabled
flag, so the following update ldif was created:
dn: m-oid=1.3.6.1.4.1.26156.30.0.0.0.1, ou=attributeTypes, cn=conneqt-config,
ou=schema
objectclass: metaAttributeType
objectclass: metaTop
objectclass: top
m-oid: 1.3.6.1.4.1.26156.30.0.0.0.1
m-name: isActiveFlag
m-description: A boolean flag to indicate if an entry is active or not
m-equality: caseIgnoreMatch
m-ordering: booleanMatch
m-syntax: 1.3.6.1.4.1.1466.115.121.1.7
m-length: 1
m-singleValue: TRUE
dn: m-oid=1.3.6.1.4.1.26156.30.0.0.1.12, ou=objectClasses, cn=conneqt-config,
ou=schema
changetype: modify
add: m-may
m-may: isActiveFlag
Now the problems I have are two-fold: firstly, when I try to add the
isActiveFlag attribute to an entry through Apache Directory Studio, it gives
a warning saying the attribute type is not allowed. Whilst I can click
through this, the second problem is that when I try to add entries
programmatically:
var name = string.Format(email={0}, emailAddress);
var entry = container.Children.Add(name, adapterMailbox);
entry.Properties[userPassword].Value = password;
entry.Properties[smtpHost].Value = smtpHost;
entry.Properties[smtpPort].Value = smtpPort;
entry.Properties[isActiveFlag].Value = isActiveFlag;
entry.CommitChanges();
It is throwing a DirectoryServicesCOMException with message “The requested
operation did not satisfy one or more constraints associated with the class
of the object.”
Anyone able to shed any light on what might be going on?
Cheers
Matthew Goudge
Developer
image001.gif
Quicksilva Systems Integration Solutions | www.qxlva.com
Tel: 01249 751 000 | matthew.gou...@qxlva.com
image002.gifimage003.gifimage004.gif
__
The Company gives no warranty as to the accuracy or completeness of
electronic mail messages sent over the Internet and accepts no responsibility
for changes made after it was sent. Any opinion expressed in this email may
be personal to the author, may not necessarily reflect the opinions of the
Company or its affiliates and may be subject to change without notice.
The information contained in this communication is confidential and/or
proprietary business or technical data. If you are not the intended
recipient, you are hereby notified that any dissemination, copying or
distribution of this communication, or the taking of any action in reliance
on the contents of this communication, is strictly prohibited. If you have
received this communication in error, please immediately notify us
electronically by return message, and delete or destroy all copies of this
communication.
Quicksilva Limited, Reg No 3860799, Incorporated at Companies House, Cardiff.
Registered Office: Langley Gate, Swindon Road, Chippenham, Wiltshire, SN15
5SE. Vat Reg No 762 8082 16.
__
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
__
Re: After adding new m-may attribute to a custom class in a schema, can't then add the attribute to an entry
Le 7/23/13 4:53 PM, Pierre-Arnaud Marcelot a écrit : Hi Matthew, Did you restart the server ? Additions don't need a server-restart and are handled on the fly. Modifications on an existing schema element, though, are not very recommended (especially if you already have data using this schema element) and I'm not really sure they are handled on the fly as well. You simply can't modify an existig schema element. You can just add a new schema element, or remove it. So a modification is a delete followed by an add. -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com
[jira] [Created] (DIRSERVER-1873) Searching on member attribute (multivalued) for groups is not working as expected
Carlo Accorsi created DIRSERVER-1873: Summary: Searching on member attribute (multivalued) for groups is not working as expected Key: DIRSERVER-1873 URL: https://issues.apache.org/jira/browse/DIRSERVER-1873 Project: Directory ApacheDS Issue Type: Bug Components: core Affects Versions: 2.0.0-M14 Environment: Windows 32 + Java 1.6 Reporter: Carlo Accorsi Hi, I have this index on my partition for the member attribute. dn: ads-indexAttributeId=member,ou=indexes,ads-partitionId=cpro,ou=partitions,ads-directoryServiceId=default,ou=config ads-indexattributeid: member ads-indexHasReverse: FALSE ads-indexcachesize: 100 objectclass: ads-index objectclass: ads-jdbmIndex objectclass: ads-base objectclass: top ads-enabled: TRUE Here is an example of two groups. Test1 has 1 member , Test2 has 2. #begin ldif version: 1 dn: uid=1374604692150,ou=groups,ou=int,o=cpro objectClass: uidObject objectClass: groupOfNames objectClass: top cn: Test1 member: uid=137460991,ou=users,ou=int,o=cpro uid: 1374604692150 description: Test1 dn: uid=1374604692151,ou=groups,ou=int,o=cpro objectClass: uidObject objectClass: groupOfNames objectClass: top cn: Test2 member: uid=137460991,ou=users,ou=int,o=cpro member: uid=137460991,ou=users,ou=int,o=cpro uid: 1374604692151 description: Test2 #end ldif Created the group and performed the following searches using Apache directory studio Version: 2.0.0.v20130131 Substring Search for (member=*) - PASS Both entries returned - OK Exact Search for (member=uid=137460991,ou=users,ou=int,o=cpro) - PASS Test 2 is returned. (hunch - value exists only once in index and so it works) Exact Search for (member=uid=137460991,ou=users,ou=int,o=cpro) - FAIL No entries returned, however all should. Substring Search for (member=u*) - FAIL No entries returned. Expected same result as (member=*) If i change the index definition to ads-indexHasReverse: I get the same results Let me know if i can help. Thanks! -- 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-940) Have schema editor populate creatorsName attribute for new objects (needed by ApacheDS)
Richard Sand created DIRSTUDIO-940: -- Summary: Have schema editor populate creatorsName attribute for new objects (needed by ApacheDS) Key: DIRSTUDIO-940 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-940 Project: Directory Studio Issue Type: Improvement Components: studio-schemaeditor Affects Versions: 2.0.0-M8 (2.0.0.v20130628) Reporter: Richard Sand When creating new schema objects, especially when loading an online schema where a bind was used, please populate (or prompt for) the creatorsName attribute, so that the schema files can be dropped into ApacheDS and used immediately. As is, ApacheDS (2.0.0-M13) fails with: [22:42:37] ERROR [org.apache.directory.api.ldap.schemaloader.LdifSchemaLoader] - ERR_10003 Failed to load schema LDIF file license.ldif java.lang.IllegalArgumentException: entry must have a valid creatorsName attribute -- 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-941) friendly name for attribute syntax not shown when creating new attribute
Richard Sand created DIRSTUDIO-941: -- Summary: friendly name for attribute syntax not shown when creating new attribute Key: DIRSTUDIO-941 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-941 Project: Directory Studio Issue Type: Improvement Components: studio-schemaeditor Affects Versions: 2.0.0-M8 (2.0.0.v20130628) Reporter: Richard Sand When creating new attributes, in the attribute syntax dropdown the OID is shown twice instead of the friendly name + OID, in contrast to the attribute editor window. See attached screenshots -- 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-941) friendly name for attribute syntax not shown when creating new attribute
[ https://issues.apache.org/jira/browse/DIRSTUDIO-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Sand updated DIRSTUDIO-941: --- Attachment: screenshot-1.jpg friendly name for attribute syntax not shown when creating new attribute Key: DIRSTUDIO-941 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-941 Project: Directory Studio Issue Type: Improvement Components: studio-schemaeditor Affects Versions: 2.0.0-M8 (2.0.0.v20130628) Reporter: Richard Sand Attachments: screenshot-1.jpg, screenshot-2.jpg When creating new attributes, in the attribute syntax dropdown the OID is shown twice instead of the friendly name + OID, in contrast to the attribute editor window. See attached screenshots -- 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-941) friendly name for attribute syntax not shown when creating new attribute
[ https://issues.apache.org/jira/browse/DIRSTUDIO-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Richard Sand updated DIRSTUDIO-941: --- Attachment: screenshot-2.jpg friendly name for attribute syntax not shown when creating new attribute Key: DIRSTUDIO-941 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-941 Project: Directory Studio Issue Type: Improvement Components: studio-schemaeditor Affects Versions: 2.0.0-M8 (2.0.0.v20130628) Reporter: Richard Sand Attachments: screenshot-1.jpg, screenshot-2.jpg When creating new attributes, in the attribute syntax dropdown the OID is shown twice instead of the friendly name + OID, in contrast to the attribute editor window. See attached screenshots -- 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
