This page is in need of updating. It does not currently reflect the most up-to-date information.
By default, Grouper relies on an external authentication service to identify authenticated principals to it through the servlet container's REMOTE_USER, so configure your shibboleth AAP to provide a suitable identifier to Grouper as REMOTE_USER. In addition, you'll need to arrange that the same identifiers are provided to Grouper through a source adapter so that shibboleth-authenticated principals can have a security context created for them. Note, if you want grouper to use REMOTE_USER or something other than tomcat authentication then you need to take out the security configuration in the web.xml if it is there: e.g. security-constraint, login-config, security-role.
6. I am using Oracle for my Grouper database, and when I try to add more groups or members, I am getting this error: "hibernate commit error: Could not execute JDBC batch update." What causes that?