• Login
    • Search
    • [[global:header.recent]]
    • [[global:header.tags]]
    • [[global:header.popular]]
    • [[global:header.groups]]
    • [[global:header.search]]

    ISLOG Logon (Windows NFC Login)

    General discussions and feedback
    7
    51
    75296
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Lokki
      Lokki Community Helper @jasok2 last edited by

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

      J 1 Reply Last reply Reply Quote 1
      • J
        jasok2 @Lokki last edited by

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

        1 Reply Last reply Reply Quote 1
        • J
          jasok2 last edited by jasok2

          @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.

          1 Reply Last reply Reply Quote 1
          • J
            jasok2 last edited by

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

            1 Reply Last reply Reply Quote 0
            • Lokki
              Lokki Community Helper last edited by

              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.

              J 1 Reply Last reply Reply Quote 0
              • J
                jasok2 @Lokki last edited by

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

                1 Reply Last reply Reply Quote 0
                • Lokki
                  Lokki Community Helper last edited by

                  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.

                  J 2 Replies Last reply Reply Quote 0
                  • J
                    jasok2 @Lokki last edited by

                    @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.

                    1 Reply Last reply Reply Quote 0
                    • Lokki
                      Lokki Community Helper last edited by Lokki

                      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.

                      J 1 Reply Last reply Reply Quote 1
                      • Maxime C.
                        Maxime C. last edited by

                        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.

                        1 Reply Last reply Reply Quote 3
                        • J
                          jasok2 @Lokki last edited by

                          @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.

                          1 Reply Last reply Reply Quote 0
                          • J
                            jasok2 last edited by

                            @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.

                            1 Reply Last reply Reply Quote 0
                            • Maxime C.
                              Maxime C. last edited by

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

                              J 1 Reply Last reply Reply Quote 0
                              • J
                                jasok2 @Maxime C. last edited by jasok2

                                @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.

                                1 Reply Last reply Reply Quote 1
                                • Maxime C.
                                  Maxime C. last edited by Maxime C.

                                  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).

                                  J 1 Reply Last reply Reply Quote 2
                                  • Andreas
                                    Andreas Community Helper last edited by Andreas

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

                                    ~Deas

                                    1 Reply Last reply Reply Quote 0
                                    • J
                                      jasok2 @Maxime C. last edited by Andreas

                                      @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
                                      Maxime C. 1 Reply Last reply Reply Quote 0
                                      • Maxime C.
                                        Maxime C. @jasok2 last edited by

                                        @jasok2 Thanks for the logs.
                                        It looks like it is incomplete, did you truncated it at the beginning or forgot to restart ISLOGService service?
                                        Otherwise maybe your reader just disappears for an unknown reason, you could also give a try with ReadCard analyze tool community version which is using the same RFID/NFC middleware (LibLogicalAccess). If your reader / tag disappears on ReadCard after a while, then the issue is on the middleware or the reader.
                                        Thank you.

                                        J 1 Reply Last reply Reply Quote 0
                                        • Maxime C.
                                          Maxime C. last edited by

                                          Small update that remove 'beep' on logon, and add data encryption on nfc tag.
                                          Stored nfc text record is now AES-128 encrypted with a random key generated at first tag use, XORed with tag UID, and base64 encoded for convenience purpose.

                                          No changes about @jasok2 current issue.

                                          You can download it here :
                                          64-bit: http://download.islog.com/islog/4.0/NG/ISLOG Logon NFC Community-4.7.0713-x64.exe
                                          32-bit: http://download.islog.com/islog/4.0/NG/ISLOG Logon NFC Community-4.7.0713-x86.exe

                                          J 1 Reply Last reply Reply Quote 1
                                          • J
                                            jasok2 @Maxime C. last edited by jasok2

                                            @Maxime-C. said in ISLOG Logon (Windows NFC Login):

                                            aybe your reader just disappears for an unknown reason, you could also give a

                                            I didn't truncate it, that was the entire text. and the file didn't even appear until after i restarted the service.

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post