• 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
    75324
    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.
    • 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
                    • J
                      jasok2 @Maxime C. last edited by jasok2

                      @Maxime-C.

                      thanks @Maxime-C the encrypted text works great :) I still get the beep at logon.

                      edit- I dont get the beep at logon, I get it at unlocking the computer if its already logged in and locked.

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

                        @Lokki said in ISLOG Logon (Windows NFC Login):

                        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.

                        OK so I seem to have had the same experience as you @Lokki of the issue just going away after a while, tonight since installing the updated software I have not had the issue again. I think we need to just keep an eye on it because @Maxime-C says that no fix was put in the new file for this.

                        I will report back with a new set of logs if this happens again.

                        EDIT- another thing iv noticed is that the login and unlock does take a good two seconds or so, perhaps at first @Lokki and I just wasn't waiting long enough....

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

                          Ok, good to know everything is working properly now.
                          I also believe this could come from the fact you didn't waited long enough before removing the ring from the reader. It is safe to keep it around 1sec on the reader.
                          I will wait for more feedback and provide an official release with dedicated web page. Thanks for your tests!

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

                            @jasok2 said in ISLOG Logon (Windows NFC Login):

                            EDIT- another thing iv noticed is that the login and unlock does take a good two seconds or so, perhaps at first @Lokki and I just wasn't waiting long enough....

                            @Maxime-C Negative... while it was playing up I tried for up to 1 minute of the ACR122 reading the ring (green light) without the computer successfully logging in. Also, the option to manually log in simply was not there which forced me to reboot.

                            Anyhow, that's resolved itself now. I'm using the new version and experience the beep as per @jasok2 's post - no beep at initial logon, beep thereafter.

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

                              Ok... well we will see if this is happening again to someone and investigate further at this moment.

                              I created a webpage for the solution to have an unique place where to get latest version, see http://www.islog.com/en/software/islog-logon-nfc-community/

                              Please feel free to suggest anything else if you believe it is missing. I hope you enjoy it otherwise ;)

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

                                Hi guys I have a weird one. Ever since ISLOG Logon (Windows NFC Login)

                                Every time I touch my ring to the phone either to login or otherwise the fitbit app on my nexus phone opens. If I uninstall the fitbit app, then it stops, but starts again if i reinstall the fitbit app.

                                Erasing my card makes the problem go away, but then i cannot login to windows using the ring.

                                Has anyone seen anything like this before? even with a different app?

                                just reaffirming the issue is on the android phone, not on windows, but removing the windows logon information on the ring makes the phone behave properly.

                                Cheers Jason

                                @Maxime-C , @Lokki

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

                                  Huh, that's interesting.I haven't experienced that one.
                                  Though occasionally it does seem like the unlock system doesn't quite go all the way and the screens will stay blank or on the lock screen until I mouse-click. Then the desktop pops up and all is good.
                                  I'm assuming that's an issue with windows just plain being odd.

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

                                    Its 100% reproducible, The text file that ISLOG puts on my ring tag somehow makes my phone open the FitBit app.

                                    Logically in my mind this is impossible!!

                                    @Maxime-C any ideas ?

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

                                      @jasok2 this is weird and not excepted. What the text record written by ISLOG Logon looks like? Any chance you can copy/past here (if you're using a test password, otherwise try to change it to a test password and confirm this is still happening)? Thank you.

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

                                        @Maxime-C here is the record. for now I'm dealing with the issue by writing the login onto the other side of the ring and twisting it around when i want to login to my computer compared to logging into my phone.

                                        Its a really weird one. I can only guess that maybe the text string is somehow the same or similar enough to the FITBIT app ID and it gets launched, or something else weird and coincidental.

                                        alt text

                                        1 Reply Last reply Reply Quote 0
                                        • M
                                          MarkGabb last edited by

                                          silly question...which nfc readers are recommended for this?

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

                                            @MarkGabb
                                            I've personally tested the ARC-122U, OMNIKEY 5021CL and OMNIKEY 6321. Different sizes and shapes but they all work well.

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