You probably need to go onto a different usenet group or find a suitable forum. This is really nitty gritty stuff. I'm not even sure how much talk their will be in the open since people make money off such technology.
Blackberry has this bluetooth badge holder than feeds your smartcard to their phone. So you wear your stinkin' badge around your neck and it communicates to all the paired devices that need the secondary authentication. Your phone is also one step in physical access to facilities via NFC.
The problem I see with any of these devices is you need to check them regularly, kind of like a license server, and from different places in the executable code. A common way to get past dongles in the dark ages was to step through the code and watch where it jumps when the port is read, then change the code in assembler. That was how dedongled programs were distributed.
There is a public version of what is known loosely as Air Force linux. Technically known as lightweight portable security. It works with usb smartcard readers. They may be documents available regarding the coding.
formatting link
In government speak, you are trying to write the CAC middleware. The public version does have the CAC provision, so the code might be acquired via a FOIA request.