...
The process will clean out any existing compiled files and staging files, and then rebuild the output file into dist/grouper-legacy-ui.tar.gz. The compilation requires the presence of a grouper.jar and grouper-ui.jar file, and the default settings assume that these exist in ../../grouper/dist/lib and ../../grouper-ui/dist/grouper/WEB-INF/lib, respectively. These will be the default locations or these files if the full Grouper project is checked out, so the grouper and grouper-ui projects will just need to be built. Otherwise, the paths to the grouper jar and grouper-ui.jar can be specified with the ant parameters -Dgrouper.jar.name=<path to grouper jar> and -Dgrouperui.jar.name=<path to grouperUi>.
Experience from Penn
At penn we use some pickers and screens from the lite-UI. We do not need or want the admin ui.
| Code Block |
|---|
Unzip the tarball
Copy the grouper-legacy-ui.jar to the WEB-INF/lib
Note: all the lite UI jsps were there already from before the upgrade, otherwise would need: WEB-INF/grouperUi
Adjust the Owasp config
org.owasp.csrfguard.unprotected.GrouperHome=%servletContext%/home.do
org.owasp.csrfguard.unprotected.GrouperExternal=%servletContext%/grouperExternal/index.html
org.owasp.csrfguard.unprotected.GrouperExternalAppHtml=%servletContext%/grouperExternal/appHtml/*
org.owasp.csrfguard.unprotected.GrouperUi=%servletContext%/grouperUi/
org.owasp.csrfguard.unprotected.GrouperUiIndex=%servletContext%/grouperUi/index.html
org.owasp.csrfguard.unprotected.GrouperUiAppHtml=%servletContext%/grouperUi/appHtml/*
org.owasp.csrfguard.unprotected.GrouperI2mi=%servletContext%/i2mi/*
org.owasp.csrfguard.unprotected.GrouperScripts=%servletContext%/scripts/*
|