295 | | Setup CA !SiteMinder to protect your Trac login URL (e.g. `/trac/login`). Also add a !LogOffUri parameter to the agent configuration (e.g. `/trac/logout`). Then modify the trac.wsgi script generated using `trac-admin <env> deploy <dir>` to add the following lines, which extract the `HTTP_SM_USER` variable and set it to `REMOTE_USER`: |
| 295 | Setup CA !SiteMinder to protect your Trac login URL (e.g. `/trac/login`). Also, make sure the policy is set to include the HTTP_REMOTE_USER variable. If your site allows it, you can set this in LocalConfig.conf: |
| 296 | {{{ |
| 297 | RemoteUserVar="WHATEVER_IT_SHOULD_BE" |
| 298 | SetRemoteUser="YES" |
| 299 | }}} |
| 300 | The specific variable is site-dependent. Ask your site administrator. If your site does not allow the use of LocalConfig.conf for security reasons, have your site administrator set the policy on the server to set REMOTE_USER. |
| 301 | |
| 302 | Also add a !LogOffUri parameter to the agent configuration (e.g. `/trac/logout`). |
| 303 | |
| 304 | Then modify the trac.wsgi script generated using `trac-admin <env> deploy <dir>` to add the following lines, which extract the `HTTP_REMOTE_USER` variable and set it to `REMOTE_USER`: |