10.0

© 2011 ABBYY. All rights reserved.
71
Web-stations settings
Web-stations are installed together with the Application Server, if Web-stations feature is selected in the Custom Setup dialog
box.
Description of possible Web-stations settings
For each web-station located at <IIS Root Directory (e.g. C:\inetpub\wwwroot)>\<Station Name>, there is a web.config configu-
ration file, whose section <appSettings> contains the following keys that define the behavior of the station:
ApplicationServer – the address of the Application Server in the format <machine name>, without «http://», has a default value
of «localhost». The key allows you to move the web-station to a different computer than the one where the Application Server is
installed, e.g. in DMZ network.
DefaultDomain – this key stores the name of the domain which will be added to the names of users who try to log into the sta-
tion. By default the value is empty. It means that the user <domain>\user must enter the whole login: <domain>\user to log into
the station. If the key has the value «domain», the domain name can be omitted and the shortened login «user» can be used. If the
user belongs to a different domain or is a local user, it is possible to specify the whole login in the format of «machine\user». In
this case, the value of the DefaultDomain key will not cause conflicts.
UseCustomAuthentication – this key allows you to switch the authentication mode used by the station: either standard IIS au-
thentication or authentication by means of FlexiCapture authentication module can be used (see «How to choose the user authen-
tication type»). If FlexiCapture authentication module is installed, the server installer sets the key value to true, otherwise – to
false.
UseHashedPageAccess
– this key determines whether automatic log off is performed when closing the browser window or a
separate browser tab. If the key value is false, log off is performed only when closing the browser window. If you close the
browser tab when working with the station without doing the log off, but the browser itself remains open, you will be able to open
the station in a new tab and continue working with it without entering a login and password.
If the key is set to true, automatic logoff is performed also when closing a separate browser tab. In this case, when you open the
station in a new tab, you will have to enter login and password. Automatic logoff is performed also when refreshing any station
page (using the Refresh command or the F5 key).
This key can be used only for the Web Scanning and Web Capture stations. By default the key is set to false.
Security Settings in FlexiCapture 10 Distributed
For user authentication, either Windows or Basic authentication or authentication by means of FlexiCapture Authentication Mod-
ule can be used.
Windows-authentication is more secure (login and password are not transmitted over the network in clear text), but this authenti-
cation method is convenient only within a domain.
Basic authentication and FlexiCapture authentication can work outside the domain as well, so these authentication types must be
used for distributed work. The main disadvantage of these authentication types is that user identification information (login and
password) are transmitted on each request to the server. Therefore, in the case of Basic authentication (or authentication by means
of FlexiCapture which uses the same protocol), SSL encryption (https) must be used. Using SSL encryption prevents from reading
or modifying data sent between client and server.
Client applications working on Basic-authentication or authentication by means of FlexiCapture Authentication Module have to
store the user name and password in a cookie to be able to pass them each time the server is accessed. In this case, security is en-
sured by the fact that these data do not get to the drive or a client machine. If a user specifies the name/password when first ac-
cessing the server, between requests these data are stored in the application memory and are deleted at log off or when closing the
browser, so they do not pose a threat to security.
To get the Application Server work over https protocol, the IIS certificate must be installed on the Application Server:
Working over https
To ensure safety, you can use https protocol. For this, you need to enable SSL support in IIS settings.
To work with IIS over HTTPS protocol, you need to obtain a certificate for the server and connect it.
Managing certificates
To open the Certificates control panel, do the following:
1. Run Microsoft Management Console. For this, open Start->Run menu, type “mmc” and press Enter.