xNT w/HID iCLASS SE


#1

My office users HID iCLASS SE readers for door access, they list compatibility with MIFARE / DESFire but can’t seem to read my xNT chip, not even to show an error state. My chip works fine on our samsung door locks, and can be read by my iphone and android phone just fine.

Is there some setup I’m missing to get it read by the HID units? is there a different chip that would be read by them. Our security folks are happy to clone my badge to my chip or allow me a second “badge” via my chip.


#2

Do you have another NTAG216 type tag in card format that you can test with to see if it will produce any results?

Card readers that expect card format tags can have trouble reading x-series tags so position as well as orientation of the tag is super critical to get proper coupling. An HF xLED would help you greatly to determine the best way to present the xNT


#3

I don’t have either, but it seems like the card is pretty easy and inexpensive to get. http://www.id-enhancements.com/nfc-pvc-card-ntag216/

Can the xNT “spoof” card format or store a piece of information (e.g. my existing employee ID) in card format? or is this more of a physical thing than a information format issue?

What is an HF xLED?


#4

The xNT’s UUID cannot be changed. It is unlikely that the reader will use data from the user memory of the xNT (that can be changed) to authenticate.

Have you scanned your existing card with an android app like TagInfo? This will tell you all you need to know if there is an implant you can use.

xLED


#5

ok, so with TagInfo i confirmed I could ready my xNT, but it could not read anything from work card/badge


#6

This is the secondary type of reader we use at the office https://www.cdw.com/product/RF-IDeas-pcProx-Plus-82-Series-RF-proximity-reader-USB/4848405?cm_cat=GoogleBase&cm_ite=4848405&cm_pla=NA-NA-RF1_MX&cm_ven=acquirgy&ef_id=Wo8a8wAAALWbOhAj:20180601181314:s&s_kwcid=AL!4223!3!198553132230!!!g!338631845896!

It will read our badges, but not my xNT as well.


#7

It could be a LF (125khz) HID card that you might be able to clone to an xEM.


#8

Thanks I guess I’m going to need another implant… has anyone made a placement guide for multiple chips in one hand?


#9

has some data…


#10

Just picking this back up, if I can’t read my work badge with taginfo on my android phone how do I know what chip would work to clone it?


#11

if you updated to Android Pie, it could be difficult to read an implant.

I have also the xIC implanted and it took with TagInfo about a minute to read it - with the older system it was quick.

The best stuff is, ask at your company. You can’t clone HF Cards (only mifare classic yould work, but at the moment there isn’t a xM1+ avaible


#12

The first thing you need to do is identify the card. Does it have any markings in the corner next to a small blue HID logo?

If you can’t read the badge with your phone, then in all likeliness, the reader you said it is is not correct.

You can’t ID HID readers from the outside. They all look the same and the can be radically different inside. It does little to identify the card.

You want answers but it requires other information and tools to gather that information. Invest in these tools and it will be a lot easier to answer your questions…

At the very least you should have an xLED HF and xLED LF. I would get the RFID Diagnostic Card. All available on the DT website.


#13

I agree. Get the diagnostic card and hold it up to the reader. That’ll give a pretty definitive statement as to whether or not it’s 125k or 13.56. I’ve personally seen and installed HID multiClass readers that do both the old 125k style and newer 13.56. It’s very possible your installer just put them in for forwards compatibility - although they look like iClass they bear a different nameplate. Could be a weird fluke or not, who knows. Most likely the reader is just getting what it thinks as garbled data and refusing to read - like when you scan an EM card on an HID reader, nothing happens. There’s also a small possibility that the reader is programmed to not even make any outwards signs that it read an invalid card although that’s unlikely unless you’re in some crazy secure facility with 3-letter agencies.

Bottom line, get a diagnostic card. They’re cheap and work for way more than just this.


#14

Unfortunately our badges are very custom and do not have any markings that would explain anything about its technology or standards. I’m 100% sure that the USB reader i linked to is the correct one (as its the one that we can request from our internal hardware store) but I do know that our physical security does flash/configure the device with some sort of custom setup before they’re usable.

I’ll order the diagnostic card and see if I can learn anything from that. Physical Security isn’t willing to give me any details about the badges or readers only to allow me to clone my existing badge if I can provide a compatible proxy for our badge.