Passing the User Context to External Applications
If Pass user context is enabled for an external application, tool or module, WebOffice 10.9 R5 calls the address via the WebOffice server and passes login, groups, roles and session identifiers.
Rules for passing the context
•The user context is only passed to addresses configured in the project as external application, tool or module with Pass user context (same scheme, host and port, same path or below), and to pages of the WebOffice instance itself.
•If the application answers with a redirect, WebOffice 10.9 R5 follows it with user context only within the configured address or within the directory of the configured page. Redirects to other addresses are followed without user context. Redirects from pages of the WebOffice instance itself are followed by the browser, also without user context.
•Use an https address for applications with user context.
•Do not configure forwarding pages (e.g. the samples under pub/custom_pages) with Pass user context.
Messages in the WebOffice log file (category CONTROLLER)
Each message names the project and – if sent by the client – the origin (layer, external application, tool or module). Addresses are logged without query.
Message (start) |
Level |
Meaning |
Remedy |
|---|---|---|---|
User context not passed to … |
INFO |
The address is not configured as external application or module with Pass user context; it is called without user context. |
Configure the address in the project as external application or module with Pass user context. |
User context (login, groups, session ids) is sent unencrypted via http to … |
WARN |
The user context is transferred unencrypted. |
Use an https address. |
Redirect from … to … not followed by the server … |
WARN |
A page of the WebOffice instance redirects; the browser follows without user context. |
Usually a forwarding page: configure the actual target directly as external application. |
Redirect from … to … followed by the server without user context … |
WARN |
The application redirects to an address that is not configured; WebOffice 10.9 R5 follows without user context. |
Configure the target as external application or module; do not configure forwarding pages with Pass user context. |
Redirect from … to … refused … |
WARN |
Redirect refused, the browser receives HTTP 502. Reasons: session identifier in the target address, POST redirect (307/308) to an address that is not configured, change from https to http, more than 5 redirects. |
Check the configuration of the application; involve its vendor if needed. |
Notice in the browser
In the cases above WebOffice 10.9 R5 sets the response header X-WebOffice-Notice with a generic text (visible in the network tab of the developer tools). Addresses, project and origin are only written to the log file.
Reverse proxy
If WebOffice 10.9 R5 runs behind a reverse proxy that rewrites the address (see Apache Reverse Proxy, header syn_urlmap), WebOffice 10.9 R5 compares the address as seen from the outside. Configure external applications, tools and modules with the scheme, host and port under which they are reachable from the outside, not with an internal address.
If an integrated external application runs on its own server or its own Tomcat instance behind the same front-end web server, the configured address must also match the scheme, host and port seen from the outside.
|
•Checking the forwarding and retrieval targets (Open Redirects) is a separate, independent setting: see Restricting Forwarding and Retrieval of External Content. •Further security settings of the application configuration: see Security. |