integration:start
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
integration:start [2018/06/14 12:41] tjotov [Other topics] |
integration:start [2018/06/14 12:52] tjotov [REMOTE_USER or any other attribute] |
||
|---|---|---|---|
| Line 14: | Line 14: | ||
| - Or Apache has to handle 403 Unauthorized - see [[integration: | - Or Apache has to handle 403 Unauthorized - see [[integration: | ||
| + | In Apache configuration just require authentication: | ||
| + | | ||
| ===== REMOTE_USER or any other attribute ===== | ===== REMOTE_USER or any other attribute ===== | ||
| User ID is sent to application in header attribute - REMOTE_USER | User ID is sent to application in header attribute - REMOTE_USER | ||
| Line 19: | Line 21: | ||
| As we use Apache you can rename it to anything else - some applications use x-forwarded-user or other user ID | As we use Apache you can rename it to anything else - some applications use x-forwarded-user or other user ID | ||
| + | Example how to send X-forwarded-user instead of REMOTE_USER: | ||
| + | RewriteEngine On | ||
| + | RewriteCond %{LA-U: | ||
| + | RewriteRule .* - [E=RU:%1] | ||
| + | RequestHeader set X-Forwarded-User %{RU}e | ||
| ===== Security remarks ===== | ===== Security remarks ===== | ||
| Apache has to be accessible only via TLS (https) | Apache has to be accessible only via TLS (https) | ||
Page Tools
