0 Replies Latest reply on Nov 21, 2018 4:07 AM by Baris KARAMUSTAFA

    Mifare Desfire EV1 Authentication Failed

    Baris KARAMUSTAFA

      Hello,

       

      I tried to authenticate using two different android devices to read an Mifare DESFIRE EV1 (AES Encrypted).

       

      First Device

      Model : Samsung Galaxy A3 (2017)

      Android Version : 8.0

       

      With this device, I can see the information of the card (hardware version, software version ...). Then I can select Application ID. When I send the Authentication Start command (AA), the card sends me the RndB key.

       

      Second Device

       

      Model : Zebra TC70

      Android Version : 5.1

       

      With this device, I can see information such as information about the card (hardware version, software version ...). Then I can select Application ID. But when I send the Authentication Start command (AA), the program returns an error.

       

      Both devices use the standard Android.NFC library. What is the reason a device has failed in this command? What does a device need to be able to authenticate with Desfire EV1?

       

      Another question is whether SAM is required for Desfire EV1 authentication?

       

      I read  Secure NFC Programmer article. But we develop the app on Xamarin platform. So we can't use SecureNfcManager APIs. We try to authenticate with APDU or Native commands.

       

      Best Regards.

       

      P.S.: For Xamarin platform we use Symbol.XamarinEMDK.dll (version: 2.6)