Thanks for your insight Carson. I will update this thread if I'm able to recreate the issue.
Original Message:
Sent: Oct 04, 2024 10:53 AM
From: chulcher
Subject: What causes profiler conflicts?
I've only ever had to use the default option.
------------------------------
Carson Hulcher, ACEX#110
Original Message:
Sent: Oct 04, 2024 10:27 AM
From: MT9
Subject: What causes profiler conflicts?
No custom fingerprints on the test cluster. I will continue to do testing to see if I can replicate the issue and if I can, I will contact TAC.
Appreciate your help. Any other recommendations or suggestions? Do you usually keep conflict detection on default medium or have you found it better to loosen the restriction? Not asking for advice for my environment, just curious what you've done historically.
Original Message:
Sent: Oct 04, 2024 10:19 AM
From: chulcher
Subject: What causes profiler conflicts?
Yes.
Do you have any custom fingerprints loaded? If not, this could be/have been a bug.
------------------------------
Carson Hulcher, ACEX#110
Original Message:
Sent: Oct 04, 2024 10:04 AM
From: MT9
Subject: What causes profiler conflicts?
I assume you're referring to the cluster wide profiler parameters? Conflict detection strict mode?
But I guess I'm failing to understand why the device name was overwritten. All testing has been done in this cluster, so I'm not sure why profiling would be incomplete in this scenario. The only variable here really is that I'm testing both Aruba and Cisco wireless systems with the same machines against this cpass cluster.
What is the behavior that leads the endpoint Device Name to update? These have to match the device attribute dictionaries and obviously Max's MBP Work is not a valid device name within Computer - Apple Mac. Mac OS X is the only valid Device Name.
Original Message:
Sent: Oct 04, 2024 09:58 AM
From: chulcher
Subject: What causes profiler conflicts?
There is a setting to modify the conflict behavior, but by default a change in the Category will result in the endpoint being marked as in conflict. Decent chance that your device was initially profiled using older (or incomplete) profiling information that has since then been updated.
------------------------------
Carson Hulcher, ACEX#110
Original Message:
Sent: Oct 04, 2024 09:22 AM
From: MT9
Subject: What causes profiler conflicts?
Hey,
I'm working on a new authentication workflow and was looking at using profiler conflicts. I saw that my computer in test had a profiler conflict. When I looked into it a bit more, I saw that the Device Name field in the endpoint was somehow overwritten with my computer's hostname. I'm running 6.11.9 in test. Curious what's happening that is causing this. Picture below.
What's even weirder is that it's trying to resolve it to an iPhone which is most certainly is not. What might be going on here?