Kbase 20962: Log File Inconsistency with Security and Blank UID Enabled
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
29/10/2007 |
|
Status: Unverified
GOAL:
Explanation of why you might see some inconsistencies in your database log file when you run Progress databases with security enabled and you allow blank UserIDs (UID).
CAUSE:
When you log in and out of a database with a user name and password (-U, -P), the following log file entries are generated:
16:24:38 Usr 12: Login by f68 on /dev/tty13. (452)
16:24:54 Usr 12: Userid is now 0001f68. (708)
16:31:41 Usr 12: Logout by 0001f68 on /dev/tty13. (453)
The 452 message indicates the system ID of the user. Message 708 and 453 indicate the Progress UID that is generated from the _User table. A look at Promon/User Control, shows the user ID as 0001f68.
If, however, you hit the escape key or cancel button when the Progress login screen is presented, you log in with a blank UID. The log file, however, does not show the UID being changed to blank.
13:10:43 Usr 61: Login by cgleiman on /dev/pts/23. (452)
14:33:37 Usr 61: Logout by on /dev/pts/23. (453)
The PROMON/User Control properly shows the user as blank.