Tracking User Access

The system tracks user access through the Web Transaction Server in several ways.

  • Transaction log

    By default, the Web Transaction Server logs all user requests in a Transaction Log, which can be tailored to contain any piece of information about the request, such as the IP address of the requestor, the user host name and usercode, the directory requested, the result status, and so on.

    Transaction logs can then be manually viewed or processed by a Web server log analyzer, such as Analog, which can show rejected requests.

  • SUMLOG file

    As the system calls the USERDATA process to authorize users, you can check the SUMLOG for entries made by USERDATA when users are sending invalid passwords.

  • LOGONCHECK procedure

    If the ClearPath MCP server has a SECURITYSUPPORT library installed, the Web Transaction Server calls the LOGONCHECK procedure for each attempted log-on. You can then code LOGONCHECK to keep its own access record.

Prev  Up  Next
Identifying Users and Allocating Access Rights  Home  Restricting and Limiting User Access