ISLOG Logon (Windows NFC Login)



  • @johnyma22 said in NFC reader/writer for windows:

    Hey guys just an update on this, I have been working w/ a third party to put together a solution for us. The experience w/ ACR122 & other readers is exceptional. This will take months to materialize so please be patient :) The third party afaik don't offer a consumer usage license yet so that's what I'm going to try to negotiate for NFC Ring Owners.

    Nice to be mentioned!
    I'm Maxime from ISLOG and we just put John's advices in practice.
    Our product ISLOG Logon is now available freely for personal use under ISLOG Logon NFC Community package.

    EDIT: for latest version to download, please go to http://www.islog.com/en/software/islog-logon-nfc-community/

    This is a first version for feedback, please be gentle :).

    -Thread forked from NFC reader/writer for windows by Andreas


  • Community Helper

    G'day Maxime,

    I've taken the ISLOG community edition for a bit of a spin and have some feedback for you.
    First off, I'll say that my installation experience was nice and easy with nothing strange or unexpected happening.
    It took me a moment to realise I needed to manually select the reader in the program setup on first run though.
    But with that out of the way I signed out and read in my unlock tag, entered my details and was up and running.
    This is all nicely done and worked well. I manually signed out a few times and logged back in with my ring with no issues.

    I hit trouble when I left the computer running while I went out, upon returning I found that the unlock program was no longer responding to a ring read and I was forced to sign in manually.
    I checked settings and all appeared to be in order, then I left the computer to do something else and when I returned again it was once more time out to the lock screen. This time there was no option to change to a password login, the message is simply that "The station is locked for user: Lokki" and the login doesn't work.

    So, that might need a little work. Otherwise, a good effort.



  • Hi @Maxime-C

    The reader I have is the ACR 122 the part number is ACR122U-A9 made by Advanced Card Systems LTD.

    When I open the application and in the RFID/NFC Reader section my reader does not appear, using the auto-detect also comes up blank.

    I have checked my device manager and the reader is installed correctly and has no issues.
    I have windows 10 x64

    I did install the reader after installing the software, in case that makes a difference. However in the drop down list i did not see my brand of reader so I suspect that at present the software does not support the ACR122 is that correct ?

    I believe from other threads that lots of people in this community have the ACR122, it would be awesome if support was included

    Cheers Jason


  • Community Helper

    @jasok2 hey fella, in the configuration window choose PCSC not NFC, the acr-122 should show up then.



  • @Lokki thanks for the tip, I will try it out when I get home :)



  • @Maxime-C and everyone else involved, this software is amazing :)

    The setup went well, but it was unclear that initial ring registration was done at the login screen. I was looking to register and setup my ring in the ISLOG Logon application after i was already logged in.

    Other than that the setup went well. I did have to uninstall my ASUS NFC Express to get it to work properly. (I doubt other people will have this issue)

    I will reply again after using it for a while.

    Cheers Jason

    edit - I just read the card with NFC Tools PRO and i have to say its not awesome that the record is in plain text, but I do recall that that is being worked on. So that will be even more awesome when that happens :)

    with the ASUS NFC express, its also a plain text file but the record is a string of gibberish encrypted data.



  • @Maxime-C , @Lokki I can also report that the application does not work once the computer is "Locked".


  • Community Helper

    I forgot to follow up on that - after a couple of reboots it appears to have settled down, and I can now unlock from screen-off if I hold the nfc ring to the reader until it beeps. I'm not sure what caused the original weirdness.



  • @Lokki Well for me it just says "The station is locked for Jason" and does nothing. but logging in works perfectly.


  • Community Helper

    Yeah, that's what I was getting for a start. I manually logged in a few times, then rebooted for something else and at some point it's started working properly.



  • @Lokki so after another reboot its working for manual locking by hitting the windows L combination. some weird beeping does happen but it works.

    I'm not sure if this is in anyway different to an actual time out lock. I will leave it on and test it again next time it times out.


  • Community Helper

    ah also when I say it "beeps" I don't mean the acr122 reader does, my computer beeps after reading for a few seconds. Then it unlocks.



  • Thanks for the global positive feedback @Lokki and @jasok2.

    I will investigate your lock tag detection issue as this should work properly. It could maybe be an issue with this specific reader I will give a try as I also have it.
    There is indeed no encryption on stored data for now but this will be quickly added as it is not a technical issue. Beep is a default feature that cannot be disable on current configuration UI but maybe it will just be disabled by default depending on feedback.

    For additional information about NFC reader type, acr122 can work as a PC/SC reader or as an NFC reader (technically, it's libnfc supported readers here in this case). But on Windows it requires specific libusb driver installation so it's generally preferable to use PC/SC.



  • @Lokki said in NFC reader/writer for windows:

    ah also when I say it "beeps" I don't mean the acr122 reader does, my computer beeps after reading for a few seconds. Then it unlocks.

    yes, i mean the same thing when i say some weird beeping goes on. this beeping on unlock is different to any noise at logon. I would be happy if the noise was gone.



  • @Maxime-C @Lokki the lock thing seems to be time related, if the computer only just locked it unlocks OK, and if its been locked for a while it doesn't work at all. the computer makes the usual noises, of registering the tag, but no unlock actually happens.



  • @jasok2 how long did you wait to reproduce it on your last test?



  • @Maxime-C. about an hour. Also once it stops working, it doesn't work again even if i do a windows L to lock and try to unlock immediately afterwards.



  • This works on my side even after 1 hour of inactivity. Does your computer entered sleep mode?
    Otherwise you can also enable logs by setting HKEY_LOCAL_MACHINE\SOFTWARE\ISLOG\LogsCardPlugin registry key to c:\islogcards.log, then restart ISLOGService service, reproduce the issue and share your log file (please indicate time of the issue reproduction).


  • Community Helper

    Nice, I'll be trying this after vacation! Exciting to see some development on desktop use for nfc readers!



  • @Maxime-C. Here is a log when it didn't work. I tried twice before just doing a manual login. this was from a Windows L and logging in straight away, there was no waiting involved this time. It just didn't work straight away.

    2016/07/13 08:54:48.097 - 2964.6636> CardPlugin-Trace: Log file 'C:\islogcards.log' begins
    
    2016/07/13 08:54:48.097 - 2964.6636> CardPlugin-Trace: cardPlugin: DllMain END
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: cardPlugin: UnInitialize begins
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: cardreader: ReleaseReaderContactless - begins
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: cardreader: ReleaseReaderContactless - ends
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: util: CleanupThreadManagement - begins for {thProcessCheckActionToDo}
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: util: CleanupThreadManagement - Structure is not used yet
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: util: CleanupThreadManagement - ends
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: util: CleanupThreadManagement - begins for {thCheckActionToDo}
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: util: CleanupThreadManagement - Structure is not used yet
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: util: CleanupThreadManagement - ends
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: util: CleanupThreadManagement - begins for {thInfoDialog}
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: util: CleanupThreadManagement - Structure is not used yet
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: util: CleanupThreadManagement - ends
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: cardPlugin: CleanupInit begins
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: cardPlugin: Initialize
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: util: Assigning provilege {SeShutdownPrivilege}
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: util: AssignPrivilege Token is NULL - Retrieving the Current process token...
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: util: Assigning provilege {SeAssignPrimaryTokenPrivilege}
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: util: AssignPrivilege Token is NULL - Retrieving the Current process token...
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: util: Assigning provilege AdjustToken error {1300}
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: util: Assigning provilege {SeIncreaseQuotaPrivilege}
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: util: AssignPrivilege Token is NULL - Retrieving the Current process token...
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: util: Assigning provilege AdjustToken error {1300}
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: cardPlugin: InitializeMemoryAndEvents begins for session ID {2}
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: cardPlugin: InitializeMemoryAndEvents - Card memory shared name {Global\ISLOGPluginData2}
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: cardPlugin: InitializeMemoryAndEvents - Action to do memory shared name {Global\ISLOGActionToDo2}
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: cardPlugin: InitializeMemoryAndEvents - IsLocked memory shared name {Global\ISLOGIsLocked2}
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: cardPlugin: InitializeMemoryAndEvents - CardEvent memory shared name {Global\ISLOGCardEvent2}
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: cardPlugin: InitializeMemoryAndEvents - Action to do event name {Global\ISLOGActionToDoEvent2}
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: cardPlugin: InitializeMemoryAndEvents - CardEvent event name {Global\ISLOGCardEventEvent2}
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: cardPlugin: InitializeMemoryAndEvents ended
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: dbinteraction: loadDataBaseFunctions begins
    2016/07/13 08:54:48.197 - 2964.6636> CardPlugin-Trace: dbinteraction: loadDataBaseFunctions ends
    2016/07/13 08:54:48.212 - 2964.6636> CardPlugin-Trace: cardPlugin: Initialize returns {0}
    2016/07/13 08:54:48.212 - 2964.6636> CardPlugin-Trace: cardPlugin: StartCheckActionToDoThread begins
    2016/07/13 08:54:48.212 - 2964.6636> CardPlugin-Trace: util: InitThreadManagement - begins for {thProcessCheckActionToDo}
    2016/07/13 08:54:48.212 - 2964.6636> CardPlugin-Trace: util: CleanupThreadManagement - begins for {thProcessCheckActionToDo}
    2016/07/13 08:54:48.212 - 2964.6636> CardPlugin-Trace: util: CleanupThreadManagement - Structure is not used yet
    2016/07/13 08:54:48.212 - 2964.6636> CardPlugin-Trace: util: CleanupThreadManagement - ends
    2016/07/13 08:54:48.212 - 2964.6636> CardPlugin-Trace: util: InitThreadManagement - Thread and events created !
    2016/07/13 08:54:48.212 - 2964.6636> CardPlugin-Trace: util: InitThreadManagement - ends
    2016/07/13 08:54:48.212 - 2964.6636> CardPlugin-Trace: cardPlugin: StartCheckActionToDoThread ends
    2016/07/13 08:54:48.212 - 2964.7136> CardPlugin-Trace: cardPlugin: ProcessCheckActionToDo begins
    2016/07/13 08:54:48.212 - 2964.7136> CardPlugin-Trace: cardPlugin: ProcessCheckActionToDo - Starting loop !
    2016/07/13 08:55:07.249 - 2964.2868> CardPlugin-Trace: cardPlugin: UnInitialize begins
    2016/07/13 08:55:07.249 - 2964.2868> CardPlugin-Trace: cardreader: ReleaseReaderContactless - begins
    2016/07/13 08:55:07.249 - 2964.2868> CardPlugin-Trace: cardreader: ReleaseReaderContactless - ends
    2016/07/13 08:55:07.249 - 2964.2868> CardPlugin-Trace: util: CleanupThreadManagement - begins for {thProcessCheckActionToDo}
    2016/07/13 08:55:07.249 - 2964.2868> CardPlugin-Trace: util: CleanupThreadManagement - Thread still active - Sending kill event
    2016/07/13 08:55:07.249 - 2964.7136> CardPlugin-Trace: cardPlugin: ProcessCheckActionToDo - Kill event received !
    2016/07/13 08:55:07.249 - 2964.2868> CardPlugin-Trace: util: CleanupThreadManagement - ends
    2016/07/13 08:55:07.249 - 2964.2868> CardPlugin-Trace: util: CleanupThreadManagement - begins for {thCheckActionToDo}
    2016/07/13 08:55:07.249 - 2964.2868> CardPlugin-Trace: util: CleanupThreadManagement - Structure is not used yet
    2016/07/13 08:55:07.249 - 2964.2868> CardPlugin-Trace: util: CleanupThreadManagement - ends
    2016/07/13 08:55:07.249 - 2964.2868> CardPlugin-Trace: util: CleanupThreadManagement - begins for {thInfoDialog}
    2016/07/13 08:55:07.249 - 2964.2868> CardPlugin-Trace: util: CleanupThreadManagement - Structure is not used yet
    2016/07/13 08:55:07.249 - 2964.2868> CardPlugin-Trace: util: CleanupThreadManagement - ends
    2016/07/13 08:55:07.249 - 2964.2868> CardPlugin-Trace: cardPlugin: CleanupInit begins
    2016/07/13 08:55:07.264 - 2964.2968> CardPlugin-Trace: cardPlugin: DllMain DETACH

Log in to reply
 

Looks like your connection to NFC Ring Forum was lost, please wait while we try to reconnect.