Security

While using the Intune extension along with EAP-TLS RADIUS wifi I'm constantly getting this message in the logs of the intune extension. Based on my policy the device can connect. The device id is in the CN but appears that when it's providing the id it's starting it with id and showing no device found.

Assuming that you use the HTTP authentication source, it seems that the Filter Query in that is set to something different than what contains the Intune Device ID:

id/ may be another field in your certificate, or the Username sent by the client. You can have a look at the Computed Attributes in Access Tracker to find the proper field:

In my case it's the Certificate:Subject-CN, but for testing I added it also as a DNS Subject alternative name. Most important is that your filter contains just the Intune ID of the client.

While using the Intune extension along with EAP-TLS RADIUS wifi I'm constantly getting this message in the logs of the intune extension. Based on my policy the device can connect. The device id is in the CN but appears that when it's providing the id it's starting it with id and showing no device found.

This is the input from access tracker from the machine. The only field that semi resembles that from the the logs is the URI however as you can see below I am using Certificate:Subject-CN

Assuming that you use the HTTP authentication source, it seems that the Filter Query in that is set to something different than what contains the Intune Device ID:

id/ may be another field in your certificate, or the Username sent by the client. You can have a look at the Computed Attributes in Access Tracker to find the proper field:

In my case it's the Certificate:Subject-CN, but for testing I added it also as a DNS Subject alternative name. Most important is that your filter contains just the Intune ID of the client.

While using the Intune extension along with EAP-TLS RADIUS wifi I'm constantly getting this message in the logs of the intune extension. Based on my policy the device can connect. The device id is in the CN but appears that when it's providing the id it's starting it with id and showing no device found.

This is the input from access tracker from the machine. The only field that semi resembles that from the the logs is the URI however as you can see below I am using Certificate:Subject-CN

Assuming that you use the HTTP authentication source, it seems that the Filter Query in that is set to something different than what contains the Intune Device ID:

id/ may be another field in your certificate, or the Username sent by the client. You can have a look at the Computed Attributes in Access Tracker to find the proper field:

In my case it's the Certificate:Subject-CN, but for testing I added it also as a DNS Subject alternative name. Most important is that your filter contains just the Intune ID of the client.

While using the Intune extension along with EAP-TLS RADIUS wifi I'm constantly getting this message in the logs of the intune extension. Based on my policy the device can connect. The device id is in the CN but appears that when it's providing the id it's starting it with id and showing no device found.

That error message suggest that you added Intune as Authentication Source, not Authorization source.

With the limited information, it may be best to work with your Aruba partner or Aruba support. As there can be many things preventing this from working, which makes guessing the right thing hard in a forum page.

This is the input from access tracker from the machine. The only field that semi resembles that from the the logs is the URI however as you can see below I am using Certificate:Subject-CN

Assuming that you use the HTTP authentication source, it seems that the Filter Query in that is set to something different than what contains the Intune Device ID:

id/ may be another field in your certificate, or the Username sent by the client. You can have a look at the Computed Attributes in Access Tracker to find the proper field:

In my case it's the Certificate:Subject-CN, but for testing I added it also as a DNS Subject alternative name. Most important is that your filter contains just the Intune ID of the client.

While using the Intune extension along with EAP-TLS RADIUS wifi I'm constantly getting this message in the logs of the intune extension. Based on my policy the device can connect. The device id is in the CN but appears that when it's providing the id it's starting it with id and showing no device found.