directory-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Patricio Demitrio <pdemit...@scoop-gmbh.de>
Subject Re: [ApacheDS] Error 56
Date Mon, 04 Feb 2013 10:10:02 GMT
Hi Kiran /everyone.

I'm trying to isolate the error here. Openam is trying the following:
----
Modify Request
        Object : 'uid=user8,ou=people,dc=example,dc=com'
            Modification[0]
                Operation :  delete
                Modification
    userpassword: '0x70 0x61 0x73 0x73 0x77 0x6F 0x72 0x64 0x31 '
            Modification[1]
                Operation :  add
                Modification
    userpassword: '0x70 0x61 0x73 0x73 0x77 0x6F 0x72 0x64 0x32 '
-------
So openam apparently is trying to remove the attribute userpassword and
create a new one with a new value, right?

Well, from apacheStudio, I'm trying to delete the attribute userpassword
and it's not letting me. Here's the error in apacheStudio:
------
Error while executing LDIF
 - [LDAP: error code 80 - OTHER: failed for MessageType : MODIFY_REQUES
  java.lang.Exception: [LDAP: error code 80 - OTHER: failed for MessageType
: MODIFY_REQUEST
Message ID : 25
    Modify Request
        Object : 'uid=user8,ou=people,dc=eiger,dc=com'
            Modification[0]
                Operation :  delete
                Modification
    userpassword: (null)
org.apache.directory.shared.ldap.model.message.ModifyRequestImpl@aec4e630:
null]
at
org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.checkResponse(DirectoryApiConnectionWrapper.java:1271)
at
org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.access$600(DirectoryApiConnectionWrapper.java:110)
at
org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper$4.run(DirectoryApiConnectionWrapper.java:726)
at
org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.runAndMonitor(DirectoryApiConnectionWrapper.java:1173)
at
org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.checkConnectionAndRunAndMonitor(DirectoryApiConnectionWrapper.java:1107)
at
org.apache.directory.studio.connection.core.io.api.DirectoryApiConnectionWrapper.modifyEntry(DirectoryApiConnectionWrapper.java:748)
at
org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifRunnable.importLdifRecord(ImportLdifRunnable.java:514)
at
org.apache.directory.studio.ldapbrowser.core.jobs.ImportLdifRunnable.importLdif(ImportLdifRunnable.java:272)
at
org.apache.directory.studio.ldapbrowser.core.jobs.ExecuteLdifRunnable.executeLdif(ExecuteLdifRunnable.java:157)
at
org.apache.directory.studio.ldapbrowser.core.jobs.ExecuteLdifRunnable.run(ExecuteLdifRunnable.java:123)
at
org.apache.directory.studio.ldapbrowser.core.jobs.UpdateEntryRunnable.run(UpdateEntryRunnable.java:59)
at
org.apache.directory.studio.connection.ui.RunnableContextRunner$1.run(RunnableContextRunner.java:113)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)

  [LDAP: error code 80 - OTHER: failed for MessageType : MODIFY_REQUEST
Message ID : 25
    Modify Request
        Object : 'uid=user8,ou=people,dc=eiger,dc=com'
            Modification[0]
                Operation :  delete
                Modification
    userpassword: (null)
org.apache.directory.shared.ldap.model.message.ModifyRequestImpl@aec4e630:
null]
-----------




Maybe the problem has been always here


On Sun, Feb 3, 2013 at 5:12 PM, Kiran Ayyagari <kayyagari@apache.org> wrote:

> forwarding to the correct ML
>
> ---------- Forwarded message ----------
> From: Emmanuel Lécharny <elecharny@gmail.com>
> Date: Fri, Feb 1, 2013 at 10:53 PM
> Subject: Re: [ApacheDS] Error 56
> To: "users@mina.apache.org" <users@mina.apache.org>
>
>
> Le 2/1/13 6:00 PM, Patricio Demitrio a écrit :
> > Hi Again,
> >
> > ads-pwdcheckquality is set to 0
> > current password for user8 is "password", and in the database is
> > {SSHA}x+TL0mJ+9p5VfxmwEgsKRZuh5Z3H+8wExAe2bw==
> > and when I open it showing the ldif perspective, it shows this:
> > e1NTSEF9eCtUTDBtSis5cDVWZnhtd0Vnc0tSWnVoNVozSCs4d0V4QWUyYnc9PQ==
>
> which is {SSHA}x+TL0mJ+9p5VfxmwEgsKRZuh5Z3H+8wExAe2bw==
>
> The pb is that 'password' once hashed does not resolve to
> {SSHA}x+TL0mJ+9p5VfxmwEgsKRZuh5Z3H+8wExAe2bw== but to
> {SSHA}Dqnp0N8cy7nj0Sn+OCZA6L0yq5ewFrPf/YvmBA==, and this is why the
> server does not find it.
>
> Now, the question is why does the hashed value is different ? Can you
> change SSHA to SMD5, and see if it's any better ?
>
>
> --
> Regards,
> Cordialement,
> Emmanuel Lécharny
> www.iktek.com
>
>
>
>
> --
> Kiran Ayyagari
> http://keydap.com
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message