ACC-V payload not returning a useable Logged In User value
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-19-2024 09:10 AM
We resolved the initial issue of ACC-V not returning any values for "logged_in_users" XML in Enhanced Discovery payloads by changing the Agent Client Collector service to run as "Local System".
Our issue now is that the value being returned is of the format firstnamelastname, and not the format of the UPN the credential actually being used for logging in first.last@domain.com. This is causing issues because ACC-V output can't be matched to the servicenow users record, since the username in the servicenow users record is the UPN from our Azure tenant.
We can not seem to get this resolved with the internal ServiceNow support teams without them recommending that we request an enhancement. Looking for guidance on how to address this seemingly very standard logon process.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-19-2024 09:30 AM
We are having the same issue! If anyone finds a solution would love to hear it
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-08-2025 09:05 PM
@JoeB21810898662 @SamD93108872890 : do you have a custom field where this would match? See the new features from ACC-V 3.3.0 (August 2023):
- New
- Software Metering and Assigned To: Support for mapping users to the right Active Directory domain: sn_acc_visibility.advanced_metering_user_mapping_field
- Changed
- SAM Advanced Metering: Allows for additional datapoints collected by osqueryd.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2025 06:12 AM
Hi Severin -
I do not see this system property - any advice on how to check if we should be seeing it or how to get it added correctly?
Thank you!
Sam
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2025 03:23 PM
@SamD93108872890: it appears the system property was renamed since then; created by default as I just tested on a PDI instance:
sn_acc_vis_content.column_name_for_user_mapping
This property is used to map user (assigned_to) to an agent CI and the SAM usage based on AD domain.
The value of this property decides which field (column) of sys_user table to be used for verifying username and domain and map it to right CI.CI.
Note:
1. If the value of the property is empty then assigned_to value of CI will be mapped based on "username" only (not domain).
2. Value of this property can be any OOTB fields or custom fields in sys_user table.
3. Username and domain formats supported: username@domain or domain\username
4. Domain is case sensitive.