OS4X Webaccess installation and configuration
Directory configuration
The user running the web server must be able to read, execute and write the following directories:
Large file support
Uploading files bigger than 2GB is a matter of the used webserver (i.e. Apache). Most common distributions include an Apache binary which is compiled with LARGEFILE support (which enables the upload of such big files). Also, your Web browser must support this feature, so it's most common to use the latest version available.
Starting from Q3/2013, OS4X Webaccess offers a HTML5 file upload mechanism which supports files bigger than 2GB. Please configure your PHP backend to a maximum file upload and POST size of at least 128MB (which is a maximum single slice size of the divided file). The maximum tested file size was 14TB.
Direct job access
Starting with OS4X 2014-12-09, you can point a user to a specific job in OS4X Webaccess. This is done by a URL "GET" parameter, namely:
job
A URL to OS4X Webaccess, pointing to job 18877 could be:
http://os4x-server/webaccess/?job=18877
If the logged in user is not allowed to view this job, nothing happens. If the user is allowed, the job will be the active tab in OS4X Webaccess after successful login.
This feature has been removed in OS4X Webaccess 6.
Pre-setting username
Starting with OS4X 2015-01-20, you can preset a username which will be filled in the login prompt. The URL parameter is:
username
A URL to OS4X Webaccess, using user "kochha" will be:
http://os4x-server/webaccess/?username=kochha
Pre-setting job id
Starting with OS4X 2015-01-20, you can preset a job which will be filled in the login prompt. The URL parameter is:
job
A URL to OS4X Webaccess, using user "kochha" will be:
http://os4x-server/webaccess/?job=529215
Password reset functionality
Starting with OS4X 2021-03-08, users with an internal authentication mode can obtain a functionality to reset their password. The following requirements must be fulfilled:
- The user must have the authentication mode "internal" (see Editing_person)
- The user must have a unique email address configured
- The functionality must not be disabled
- A text template is configured for the mail process
- A MTA is configured at the OS4X backend server (see OS4X VMware virtualized image - mail configuration)