beautypg.com

Example 1, Example 2 (recommended for single user group), Example 3 – Echelon SmartServer 2.2 User Manual

Page 530

background image

SmartServer

2.2 User’s Guide

531

respectively. The WebParams.dat files included in these examples provide the recommended
solutions for these scenarios.

Example 1

Users: Single user group (or multiple user groups with only the system web pages secured).
Security Level: Minimal password protection.
Types of Pages Accessed: Factory Web pages only (no custom web pages).
WebParams.dat file:

(Users)
all:ilon:ilon
(Locations)
everywhere:*.*.*.*
(Realms)
/user/Echelon/Menu.html:all:everywhere
(Aliases)

Note: This is the factory default setting. It provides Login security to all factory Web pages.

Example 2 (recommended for single user group)

Users: Single user group.
Security Level: Complete password protection.
Types of Pages Accessed: Factory and custom Web pages.
WebParams.dat file:

(Users)
all:ilon:ilon
(Locations)
everywhere:*.*.*.*
(Realms)
/WSDL/*:all:everywhere
/user/*:all:everywhere
(Aliases)

Note: If you are using SOAP applications or the Web Binding feature, provide a user name and
password for these features to work and create a separate user group and realm for SOAP users. The
WebParams.dat file would then appear as follows:

(Users)
all:ilon:ilon
soapuser:ilon1:ilon
(Locations)
everywhere:*.*.*.*
(Realms)
/WSDL/*:all:everywhere
/WSDL/*:soapuser:everywhere
/user/*:all:everywhere
(Aliases)

Example 3

Users: Two user groups (“all” and “enduser”).

Security Level: Factory system Web pages secured only.

Types of Pages Accessed: Factory Web pages though the frameset (not accessed directly). SOAP
applications and Web connections can access the SmartServer without password protection. See
example 4 for how to implement full password protection for this scenario.

WebParams.dat file: