TapLinx

Forum / MIFARE SDK / TapLinx

  • 17. August 2016 at 15:32
    Dear Mifare,

    we are about to kick-off a new project for a client, aimed to read Mifare Plus X cards. Masterkeys are to be stored in SAM AV2 modules.
    In the planning phase, we’ve opted to use the Mifare SDK Advanced version, because that seems to cover the required functionality best.
    Recently, we’ve received an email notification from You, that the Mifare SDK is about to be rebranded as TapLinx, which also affects its licensing and the API itself.
    Could You please provide us more information regarding the above mentioned changes?
    What is the expected launch date for the new product line? How can we get a copy of the documentation of the API, and the functionality?

    Thanks in advance,
    Sandor

    + 0  |  - 0

    Re: TapLinx

    18. August 2016 at 13:07
    Dear Sandor,

    Yes, we are in the process for releasing TapLinx now. You can expect the release in the next two weeks.

    The architecture has changed. This means that you cannot change to TapLinx without code modifications. But the changes are moderate. The name and the meaning of most of the classes are the same.

    The Advanced SDK contains an own keystore. This keystore does not exist in TapLinx anymore. You are free to use the crypto provider you want. The sample app, which comes with the SDK, uses Bouncy Castle as provider.

    You are using the MIFARE SAM AV2. It might be interesting to know that you can use the SAM, if it is integrated in your system and you are able to initialize a Java key class from the SAM (javax.crypto.SecretKey it is used in TapLinx as key reference). Please take in mind, that there is no standard API to communicate with the SAM, therefore it cannot be integrated in the TapLinx SDK.

    Regards,
    The MIFARE Team

    + 0  |  - 0

    Re: TapLinx

    19. August 2016 at 9:46
    Dear SDK Team,

    thanks for your response.
    As we haven't started the development yet, we have no hands-on experiences with the Mifare SDK.
    We have studied the available documentations though, and it seems, that there is a pretty good abstraction for example for the handling of the SAM module there (SamAV2 hardware keystore class).
    Are you saying that such functionality is going to be discontinued in TapLinx, or is it going to have the corresponding (high level) means of interacting with the SAM module?

    Regards,
    Sandor

    + 0  |  - 0

    Re: TapLinx

    13. September 2016 at 9:54
    Hi Sandor,

    Then you should start with TapLinx. But take in mind, the SAM AV2 is not supported by default. You have to implement the SAM interface and this depends on the driver of the contact interface.

    Regards,
    The TapLinx Team

    + 0  |  - 0

    Re: TapLinx

    13. September 2016 at 10:56
    Dear TapLinx Team,

    thank You for the information!

    Regards, Sandor
    + 0  |  - 0

    Re: TapLinx

    13. September 2016 at 14:20
    Dear TapLinx Team,

    We would prefer to use a ready made SAM AV2 API, instead of implementing our own. What are the possible options?
    - is the previous Mifare Advanced SDK completely discontinued, or is it still an option to start development based on it (using its supported HID readers)?
    - can you provide a SAM Interface implementation for the HID readers (those, that were already supported by the Advanced SDK)?
    - do you know about any other SAM Interface implementations, that one could rely on? We understand, that we should use the javax.crypto.SecretKey class with a reference to the key stored in the SAM module, but are there any known crypto providers for some specific readers?

    Thank you for your help,
    Sandor
    + 0  |  - 0

    Re: TapLinx

    14. September 2016 at 10:42
    Dear Sandor,

    Yes, the MIFARE SDK is replaced by the TapLinx SDK. You can still use it, but the development has terminated.

    The problem of supporting a SAM AV2 is the contact interface. Some phones has a separate SIM card slot, but the most don’t. If you use a contact reader connected via USB cable, you have to use the driver of the reader and every manufacturer provide its own driver. There is no standard interface for a SIM card on an Android system and this is the reason why you cannot support the SAM within from TapLinx on the phone.

    I know, that the HID Omnikey 6121 Reader was supported by the MIFARE SDK. But the 6121 is not continued and the support has stopped. I have to check, if the 6121 is supported as hardware key store in the last release of the MIFARE SDK.

    Regards,
    The TapLinx Team
    + 0  |  - 0
Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic.