If you want to use apache authentication, you can do that. Generally you should not use a password file (use grouper built-in authn instead), if you use LDAP or something else it could be useful
If you are using apache ldap authn, manage users in your ldap. This is an example using a password file which is not convenient in container, but as an example
[appadmin@i2midev1 bin]$ sudo htpasswd /etc/httpd/conf.d/users.pass username |
Note the file locations in the container are listed in the v2.5 container documentation
File | Value | Description | |
---|---|---|---|
grouper.hibernate.properties | grouper.is.ws.basicAuthn=false | This is the default provided with container, do not overlay | |
web.xml | No security-constraints or login-configs | This is the default provided with container, do not overlay | |
server.xml | ajp 8009 connector element: tomcatAuthentication="false" | This is the default provided with container, do not overlay Tomcat is not doing authn so that attribute needs to be false | |
grouper-ws.properties | ws.security.non-rampart.authentication.class = | This should be blank (get remote_user) This is the default provided with container, do not overlay | |
grouper-www.conf | Customize this directive with the apache authn config
| Configure apache authn here |