000015082 - AxM 6.1 - GUIDs not explained properly in I&C guide for enhanced aserver.log

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000015082
Applies ToAccess Manager 6.1
All OS & All Datastore
IssueAxM 6.1 - GUIDs not explained properly in I&C guide for enhanced aserver.log

On page 228 of the Install and Config guide, enhanced logging GUID is documented as such:

"Contain globally unique identifier (GUID) for every record of log message. All related events must have the same GUID. This GUID is related to correlate a single event. For example, Authenticate."

The documentation does not explain this properly and is therefore susceptible to be misinterpreted as to how the GUID is used and appears in the logs per transaction.

ResolutionThis description is not complete.  When a user accesses a resource, the agent calls APIs checkResource, authenticate and authorize. These three calls are atomic, and hence the operations related to each will have same GUIDs.  While the documentation may be open to be misinterpreted, this GUID is not a transactional ID.  AXM is stateless, hence grouping a set of state operations by a transaction id is not possible.
Legacy Article IDa48535

Attachments

    Outcomes