The ftprops is schema problem due to recent changes. Can you do a git pull on the fortress-core repo and try again? Shawn
> On Dec 2, 2016, at 1:51 PM, Martijn Dashorst <[email protected]> > wrote: > > When running step 1 I encountered some problems: > > - the run_tests.sh script doesn't work on Mac OS X (El Capitan) due > to a missing parameter for sed. I had to insert '-e' before the > replacement expression > > - running the script fails a test: > > 2016-12-02 20:44:022 ERROR PropertyMgrImplTest:94 - addProperties > caught SecurityException rc=1003, msg=add entity properties[Group] > caught LDAPException=attribute 'ftProps' not allowed > org.apache.directory.fortress.core.UpdateException: add entity > properties[Group] caught LDAPException=attribute 'ftProps' not allowed > at > org.apache.directory.fortress.core.impl.PropertyDAO.addProperties(PropertyDAO.java:76) > at > org.apache.directory.fortress.core.impl.PropertyP.addProperties(PropertyP.java:53) > at > org.apache.directory.fortress.core.impl.PropertyMgrImpl.add(PropertyMgrImpl.java:49) > at > org.apache.directory.fortress.core.impl.PropertyMgrImplTest.addProperties(PropertyMgrImplTest.java:86) > at > org.apache.directory.fortress.core.impl.PropertyMgrImplTest.testCrudProperties(PropertyMgrImplTest.java:63) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at junit.framework.TestCase.runTest(TestCase.java:176) > at junit.framework.TestCase.runBare(TestCase.java:141) > at junit.framework.TestResult$1.protect(TestResult.java:122) > at junit.framework.TestResult.runProtected(TestResult.java:142) > at junit.framework.TestResult.run(TestResult.java:125) > at junit.framework.TestCase.run(TestCase.java:129) > at junit.framework.TestSuite.runTest(TestSuite.java:252) > at junit.framework.TestSuite.run(TestSuite.java:247) > at > org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:86) > at > org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:283) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:173) > at > org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153) > at > org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:128) > at > org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:203) > at > org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:155) > at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103) > Caused by: > org.apache.directory.api.ldap.model.exception.LdapSchemaViolationException: > attribute 'ftProps' not allowed > at > org.apache.directory.api.ldap.model.message.ResultCodeEnum.processResponse(ResultCodeEnum.java:2086) > at > org.apache.directory.ldap.client.api.LdapNetworkConnection.modify(LdapNetworkConnection.java:2342) > at > org.apache.directory.ldap.client.api.LdapNetworkConnection.modify(LdapNetworkConnection.java:2351) > at > org.apache.directory.ldap.client.api.LdapConnectionWrapper.modify(LdapConnectionWrapper.java:238) > at > org.apache.directory.fortress.core.ldap.LdapDataProvider.modify(LdapDataProvider.java:303) > at > org.apache.directory.fortress.core.impl.PropertyDAO.addProperties(PropertyDAO.java:71) > ... 24 more > > But I doubt that either of these steps will solve the > ClassNotFoundException in wildfly. > > Martijn > > > On Fri, Dec 2, 2016 at 4:09 PM, Shawn McKinney <[email protected]> wrote: >> >>> On Dec 2, 2016, at 8:38 AM, Laura van de Weerd <[email protected]> >>> wrote: >>> >>> We've followed the instructions given by Shawn to Martijn and have a >>> running docker image for the LDAP environment. When we start the fortress >>> commander in wildfly 10.1 and try to login we get the following >>> ClassNotFoundException. Is there any step we've missed in setting things up? >> >> Hi Laura, >> >> There are a couple of additional steps to prepare the docker image to >> fortress-web usage. >> >> 1. from the location of your directory-fortress-core repo: >> >> # export JAVA_HOME=… >> # docker/run_tests.sh >> >> This will load your docker image with some ldap test data and configs. >> >> 2. from the location of your directory-fortress-commander repo: >> >> ``` >> mvn install -Dload.file=ldap/setup/FortressWebDemoUsers.xml >> ``` >> >> This will load your docker image with sample security policies to test with. >> >> Let me know if you have problems with either of these two steps. >> >> Thanks, >> Shawn > > > > -- > Become a Wicket expert, learn from the best: http://wicketinaction.com
