Analyzing the License Verification Failure

Forum / MIFARE SDK / Analyzing the License Verification Failure

  • 4. February 2019 at 11:10
    All TapLinx users,

    In a security rollout the registration server for TapLinx was updated. After the update, only SSL connections with TSL 1.2 (and higher) are accepted. This affect devices with Android 4.4 and lower (Kitkat) which does not support TSL 1.2 by default.

    Currently we cannot give any suggestion how to fix older devices.

    Please take in mind, a registration of an Android device is not mandatory if you use it offline (never activate an internet connection).

    The TapLinx team

    + 1  |  - 3

    Re: Analyzing the License Verification Failure

    13. February 2019 at 15:55
    Please I have clients complaining that solutions I deployed are displaying registration error and cannot read their cards. These solutions require internet access and cannot do offline verification. Please provide a solution.
    + 0  |  - 0

    Re: Analyzing the License Verification Failure

    30. April 2019 at 13:34
    Is it possible to change the SDK, that on Android >= 16 and < 20 to set TLS 1.2 in the socket for the registration request as default, because it supports it, but it is not enabled by default? It can't be changed from outside of the library - at least without google services installed.
    + 0  |  - 0

    Re: Analyzing the License Verification Failure

    24. July 2019 at 15:08
    Users can interface with datasets through Analyze in Excel on the off chance that they have read consent on the fundamental dataset. A user could have this in a few different ways, such as being an individual from the workspace containing the dataset, having a report. online dissertation proposal service
    + 0  |  - 0
Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.