Ok, I see the entries now, and it looks like they are correct and the policies exist as well. Is there a global config setting that needs set?
----- Original Message ----- From: "Shawn McKinney" <[email protected]> To: [email protected] Sent: Thursday, May 4, 2017 5:22:30 PM Subject: Re: Unit Tests It’s an operational attribute so you’ll have to explicitly tell the the client to pull them. What are you using? Directory studio has an option to pull them, right-click on the entry, fetch operational attributes. Shawn > On May 4, 2017, at 3:04 PM, Chris Pike <[email protected]> wrote: > > So I was originally having problems because the attribute "pwdPolicySubentry" > wasn't recognized because I wasn't loading the policy module. Once I got that > loaded, it looks like it is being added to users when I step through code, > but I don't see the attributes when I query the users. > > > > > ----- Original Message ----- > From: "Shawn" <[email protected]> > To: [email protected] > Sent: Thursday, May 4, 2017 3:44:31 PM > Subject: Re: Unit Tests > > You can still use slapd.conf with latest version of openldap but of course > don't have to. The likely cause is slapd config doesn't have pwpolicy > enabled. . In your case it will be under cn=config. > Could also be fortress config. Maybe server type not openldap. > -------- Original message --------From: Chris Pike <[email protected]> Date: > 5/4/17 12:26 PM (GMT-06:00) To: [email protected] Subject: Re: > Unit Tests > I am running a newer version, which I don't think has the slapd.conf file > anymore... > > > > ----- Original Message ----- > From: "Shawn McKinney" <[email protected]> > To: [email protected] > Sent: Thursday, May 4, 2017 12:06:57 PM > Subject: Re: Unit Tests > > Definitely an openldap pw policy issue. Is that overlay enabled in your > server? Here’s the error: > > /** > * The password change failed because User is not allowed to change > password. > */ > public static final int USER_PW_MOD_NOT_ALLOWED = 1018; > > Can you send your fortress.properties and slapd.conf config? (pw’s redacted > of course) > > > Shawn > > >> On May 4, 2017, at 9:55 AM, Chris Pike <[email protected]> wrote: >> >> Shawn, >> >> I'm working on running the unit tests, and am getting an error when changing >> password >> >> junit.framework.AssertionFailedError: >> org.apache.directory.fortress.core.model.User.changePassword user >> [jtsTU2User1] user not authorized to change password, ldap rc= Fortress >> rc=1018 >> at junit.framework.Assert.fail(Assert.java:57) >> at junit.framework.TestCase.fail(TestCase.java:227) >> at >> org.apache.directory.fortress.core.impl.AdminMgrImplTest.changePasswords(AdminMgrImplTest.java:340) >> at >> org.apache.directory.fortress.core.impl.AdminMgrImplTest.testChangePassword(AdminMgrImplTest.java:312) >> >> My testing environment is slightly modified from last time I ran the tests, >> so I am assuming some sort of config issue. Any ideas? >> >> Thanks, >> >> ~Chris >>
