Translations:Modules/HTTP/10/en

To configure and control this module, you have the configuration page of the OpenSCADA control interface (Fig.3) where you can perform:

• Control for the active authentication sessions.
• Configuring:
  • Rules of accessing for deny and allow. Any line of the rules of accessing is a different rule and you can use here templates, like to "*/WebVision/*"), or regular expressions, like to "/[^/]+/WebVision/.+/". Useful entries for:
    • Deny:
      • "*/WebCfgD/*" — the module WebCfgD completely;
      • "*/WebVision/*tmplSO/*" — the VCA project "tmplSO" of the module WebVision.
    • Allow:
      • "*" — all, excluding the deny;
      • "/^[^/]+/[^/]*$/" — pages of the module with all their resources;
      • "*/login/*" — the login page;
      • "/^[^/]+/WebVision/[^/]*($|\?)/" — the WebVision module main page without the VCA projects accessing;
      • "/^[^/]+/WebVision/.+_aviariesOril\d*/.*/" — the VCA project "aviariesOril" of the module WebVision.
  • HTML-template of the user interface and user main-page. In the HTML-template's fields you must specify an address of the file HTML/XHTML, which will be used for formation of the internal-service and main-page interfaces. Internal-service interfaces for example, it's the WEB-modules selection, the login page and like ones of the WEB-modules. From the template required correct XHTML, allowing parse the file by XML-parser, and the presence of the tag "#####CONTEXT#####" at the location of the dynamic content, for internal-service interfaces it's necessarily. Resource files of the templates represented by images, CSS and JavaScript files and their are searching from the directory in which located the specified template file and from the current directory. If errors are found in the template there will be use a standard builtin interface. For different, to the language, template file you can add the language suffix to the file end like "{My template}_{lang}.html" but select the generic-base template file "{My template}.html" into these configuration fields. For the templates example you can see to the most used templates:
    • Internal-service and main-page interfaces template, includes the modules index.
    • Main-page's template with a direct link to the AGLKS main interface by UI.WebVision and without the WEB-modules index.
    • Main-page's template with a strong redirection to the AGLKS main interface by UI.WebVision.
  • DB of the active authentication sessions provides an external table of the active authentication sessions — "HTTP_AuthSessions", which is enabled for not empty value and provides a possibility of sharing the authentication between different OpenSCADA stations and its short storing at the station shut down time.
  • Authentication UID generation space, accessible with the common authentication sessions table to guaranty the cookie difference for different OpenSCADA processes.
  • Lifetime of the authentication, list of the users allowed for authentication and set up of the automatic login.