For standalone use - provision fobs
Closed this issue · 1 comments
It would be useful to have an MQTT command to provision a fob to current AID/AES keys on the card reader itself.
This is for cases where the reader is used on other systems and not on the cloud/control back end.
This should have JSON payload allowing the current card master key to be specified, or an option such that one is created. A response can provide the newly allocated key for the application created. Options to create afile, or just a simple name record may make sense as stand alone systems may not use the afile logic for autonomous working.
The issue is the DES coding, we have code for this that could be run on the ESP now, but we also now have code in the DESFire repository for local working with a reader via a serial link. So closing as not sensible.