--On Friday, November 16, 2012 12:17 AM +0000 beni.anil(a)gmail.com wrote:
> Please let me know if i am going wrong.
As I already told you. Use the openldap-technical mailing list. This ITS
will be closed, again.
<http://www.openldap.org/lists/mm/listinfo/openldap-technical>
--Quanah
--
Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
--On Thursday, November 15, 2012 5:27 PM +0000 beni.anil(a)gmail.com wrote:
> Full_Name:
> Version: 2.4.20
> OS: RHEL 6.3
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (14.140.116.135)
The ITS system is for filing bug reports. For configuration issues such as
yours, please use the openldap-technical mailing list.
I will note that your reported version of OpenLDAP is extremely old.
Although this may be unrelated to the issue you are facing, you would be
well served to use something current.
This ITS will be closed.
--Quanah
--
Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration
Michael Ströder wrote:
> Jan Synacek wrote:
>> On 11/08/2012 08:14 AM, michael(a)stroeder.com wrote:
>>> FYI: I sent output of bt full to Jan with some data stripped because of
>>> privacy concerns.
>>>
>>> Note that the entry for which constraint checking is done is added to the
>>> database. So something might be wrong *after* the check.
>>
>> Can you please try the attached patch?
>
> It seems to work. But I will test it during the next days more thoroughly.
No more seg faults so far in my setup which uses slapo-constraints quite
heavily. So I'd appreciate if Jan's patch lands in RE24 branch.
Ciao, Michael.
Full_Name: Shawn McKinney
Version: all
OS: all
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (99.34.196.221)
Hello,
We have created a new application, called EnMasse.
EnMasse is a web application that implements RESTful Web services to interface
with Fortress/OpenLDAP. EnMasse was built using established Open Source
technologies including Apache CXF (web services stack), Spring Framework (glue),
Maven (dependencies) and JAXB (data binding layer) and runs inside any
reasonably compliant Java Servlets container. EnMasseÂ’s service access decisions
are made using declarative Java EE and Spring security policy hooks that are
wired to connect back to the Fortress RBAC component itself.
This product has not been published and we would like to release it as one of
the products under OpenLDAP family of products.
What we would like from OpenLDAP foundation is the following:
1. Separate GIT project called EnMasse.
2. Mailing list for developers and users to communicate with project team.
3. Issue tracking for EnMasse project.
4. Project page for overview and how to find out more information.
I have uploaded one package, entitled enmasse-openldap-submission.zip to our FTP
server that contains the source, documentation and other items for you to look
at.
host: joshuatreesoftware.us
user: jtreeguest
pw: Guest123
Everything under the /target folder contain generated project artifacts
including deployable web archive (war) and javadoc. These artifacts will not be
checked into GIT.
The source is located /src folder in the package.
Statement of origin for submitted works:
The contributed EnMasse works described above were provided by JoshuaTree
Software, LLC and referenced in this ITS were created by JoshuaTree Software,
LLC,
who is the exclusive owner of the contributed works. The contributed works are
made available as indicated in the copyright and license statements attached to
the work.
Sincerely,
Shawn McKinney
Principal, JoshuaTree Software, LLC
--On Friday, November 09, 2012 6:59 AM +0000 masarati(a)aero.polimi.it wrote:
>
>> Full_Name: Roy Luckow
>> Version: 2.4.30
>> OS: Win Server 2003
>> URL: ftp://ftp.openldap.org/incoming/
>> Submission from: (NULL) (212.4.225.4)
>>
>>
>> LDAP Search for attribute "telexNumber" doesn't work.
>> If I do a search filter "(telexNumber=*)" --> Then I get my results
>> (total of
>> 4600 hits). If I set the search as "(telexNumber=*1*)" --> Then I get the
>> Message "No entries matched"
>
> This is by design: "telexNumber" has no matching rule. This ITS will be
> closed.
I would note that you can force matching rules to apply to a particular
attribute during a search. You might try the matching rules for
telephoneNumber.
Hope this helps,
Quanah
--
Quanah Gibson-Mount
Sr. Member of Technical Staff
Zimbra, Inc
A Division of VMware, Inc.
--------------------
Zimbra :: the leader in open source messaging and collaboration