On Wed, Jun 3, 2015 at 5:28 PM, Emmanuel Lécharny <[email protected]> wrote:
> Le 03/06/15 11:20, Kiran Ayyagari a écrit : > > On Wed, Jun 3, 2015 at 5:08 PM, Fabrice Aupert <[email protected]> > wrote: > > > >> Hi Kiran, > >> > >> Thanks for your quick answer. > >> > >> [LDAP: error code 53 - UNWILLING_TO_PERFORM: failed for MessageType : > >> ADD_REQUES > >> java.lang.Exception: [LDAP: error code 53 - UNWILLING_TO_PERFORM: > failed > >> for MessageType : ADD_REQUEST > >> Message ID : 32 > >> Add Request : > >> Entry > >> dn[n]: cn=pwdPolicy,cn=mypolicies,ou=schema > >> objectClass: container > >> objectClass: top > >> cn: pwdPolicy > >> : ERR_83 Cannot add an entry on cn=pwdPolicy,cn=mypolicies,ou=schema] > >> at org.apache.directory.studio.connection.core.io.api. > >> > DirectoryApiConnectionWrapper.checkResponse(DirectoryApiConnectionWrapper. > >> java:1280) > >> > > this is from Studio side, do you have the stacktrace from server log? > > I suspect that the pb is that the data are added into the schema, which > has a pretty strict structure. > > doh, right very likely. Fabrice, you have to inject this into config partition (ou=config) but you need to inject PasswordPolicies as per the way ApacheDS understands them. The password policies are stored under ou=passwordPolicies,ads-interceptorId=authenticationInterceptor,ou=interceptors,ads-directoryServiceId=default,ou=config Take a look at the default ppolicy example ads-pwdId=default,ou=passwordPolicies,ads-interceptorId=authenticationInterceptor,ou=interceptors,ads-directoryServiceId=default,ou=config And also, you can use Studio to create password policies in an easier way. -- Kiran Ayyagari http://keydap.com
