Initial Security Settings

Security Manager Service > Security Manager Setup > Vapor Application Example

Initial Security Settings

The next thing that must be decided is what initial security settings to give the application. In Vapor's case, let's say that there are going to be five custom application privileges, over and above the available system privileges already listed in VTS\SecurityManager.ini. Let us also assume that we want there to be five minutes of inactivity before automatic logoff is triggered, out of a maximum of sixty minutes; that we do not want there to be blank passwords allowed in our application; and that we do not want there to be feedback displayed for password entries.

VTS\SecurityManager.ini contains the base security settings for all VTS applications, and hence our settings should not be placed there; rather, the information can be stored in either OEM[1]\SecurityManager.ini or in App\SecurityManager.ini (i.e. either in the OEM layer's SecurityManager.ini file, or in the application layer's SecurityManager.ini file). However, since the App\SecurityManager.ini file contents may be modified at runtime, it is probably better to put the information OEM[1]\SecurityManager.ini as follows:

[SecurityManager-Admin]

AutoLogoff = 5

AutoLogoffMin = 0

AutoLogoffMax = 60

PasswordMinLen = 1

PasswordDisplay = 0

[SecurityManager-PrivApp]

PrivBitsTotal = 5

PrivDesc0 = Application $image\help0007_wmf.gif$ 0