Shawn, 1. You need to clone the repo, then checkout the branch you want, so
git clone https://github.com/PennState/directory-fortress-core-1.git git checkout feature/addPermAttrAndUserRoleConstraints 2. The audit tests still fail in my environment, I'll look through your updated documentation, might be a problem with how I am installing openldap 3. Right now, addRoleConstraint is a two step process, but would be easy to do it as part of the "assignUser( UserRole uRole )" method as well 4. I'll work on running the performance tests. Thanks for taking a look! ~Chris ----- Original Message ----- From: "Shawn McKinney" <[email protected]> To: [email protected] Sent: Sunday, January 31, 2016 12:45:55 PM Subject: Re: Fortress Constraints > On Jan 31, 2016, at 10:49 AM, Shawn McKinney <[email protected]> wrote: > > Let’s get before & after performance impacts of these changes (once inserted > into access mgr). There is a short section in the README of how to run the > jmeter tests. I recommend tests A & B. We’ll definitely want same for > sessionPermissions but I’ll need to add the test case. Let me know if you > need help getting this running. Added the perf test for sessionPerms: 2. The .jmx files located in [.src/test/jmeter](.src/test/jmeter) folder are used to control test settings for the following: C. Fortress SessionPermissions: [src/test/jmeter/ftSessionPerms.jmx](src/test/jmeter/ftSessionPerms.jmx) 3. From **FORTRESS_HOME** folder, enter the following command from a system prompt: C. Fortress SessionPermissions: ``` mvn -Ploadtest-fortress-sessperms jmeter:jmeter ``` Shawn
