This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | |||
integration:overview [2019/08/01 08:34] tjotov removed |
— (current) | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ===== No-Code integration overview ===== | ||
- | {{: | ||
- | - User opens a web application | ||
- | - Apache resolves it with code 401 - unauthenticated | ||
- | - [[integration: | ||
- | - As soon as user authenticates page is reloaded and proxypass used to retrieve the back-end application for user | ||
- | - Or Apache has to handle 403 Unauthorized - see [[integration: | ||
- | In Apache configuration just require authentication: | ||
- | | ||
- | ===== REMOTE_USER or any other attribute ===== | ||
- | User ID is sent to application in header attribute - REMOTE_USER | ||
- | In ADUCID AIM it is called UDI | ||
- | 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 ===== | ||
- | Apache has to be accessible only via TLS (https) | ||
- | Back-end application has to be separated and accessible only from Apache (http, ajp, ...) | ||
- | Apache installed for ADUCID shouldn' | ||
- | Headers from client are not transported to the back-end as ProxyPass is used (unless you configure Apache to do it) | ||
- | So if users sents REMOTE_USER to Apache, it is wiped out and target application won't see it | ||
- | |||
- | ===== Technical overview ===== | ||
- | {{: | ||
- | |||
- | This picture describes internal components of No-Code integration solution. | ||
- | |||
- | ===== Other topics ===== | ||
- | * [[integration: | ||
- | * [[integration: | ||
- | * [[integration: |