Issue metadata
Sign in to add a comment
|
Windows Security Smart Card "Please enter your Pin" prompt is missing box to enter pin
Reported by
gscottma...@gmail.com,
Oct 30
|
||||||||||||||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36 Steps to reproduce the problem: 1. Select Smart Card Logon for any site that requires/offers that option 2. 3. What is the expected behavior? The Windows Security Smart Card login popup window should have a PIN entry box What went wrong? The Windows Security Smart Card Login popup windows did not have a entry field for the PIN Did this work before? Yes Unsure Chrome version: 70.0.3538.77 Channel: stable OS Version: 10.0 Flash Version: 31.0.0.122 This works in MS Explorer.
,
Oct 31
The issue looks similar to issue id: 880835. Hence, merging into the issue id: 880835. Please feel free to undupe if not the case. Thanks...!!
,
Oct 31
krajshree: I was following that issue, but they only fixed the issue for Windows 7. It still doesn't work in Windows 10. Thanks. How do I undup?
,
Oct 31
Unmerging, based on the reporter saying it's not resolved. 1) Can you please include your current chrome://version ? Please include the full Chrome version, as well as the Variations 2) As you're on Windows, is it possible to download Chrome Canary ( see https://www.google.com/chrome/canary/ ), which does not replace/alter your existing Chrome installation, and test there? Chrome and Chrome Canary can run side by side on Windows, and so you can potentially test to see if it's resolved there. 3) Can you describe more about which Smartcard you're using, if you know? For example, are you using CAC, PIV, a national ID card (if so, what country), etc? 4) Assuming it's not resolved in Canary, using Canary, can you open chrome://net-export and then, in a separate tab, attempt to login to a site that requires your smart card? You can then attach the net-export log to this bug, which will include additional diagnostics about the smartcard driver and middleware that may help us further pinpoint the issue. Thanks!
,
Oct 31
,
Nov 1
1) Can you please include your current chrome://version ? Please include the full Chrome version, as well as the Variations Google Chrome 70.0.3538.77 (Official Build) (64-bit) (cohort: 70_77_Win) Revision 0f6ce0b0cd63a12cb4eccea3637b1bc9a29148d9-refs/branch-heads/3538@{#1039} OS Windows JavaScript V8 7.0.276.32 Flash 31.0.0.122 C:\Users\gmajor\AppData\Local\Google\Chrome\User Data\PepperFlash\31.0.0.122\pepflashplayer.dll User Agent Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36 Command Line "C:\Users\gmajor\AppData\Local\Google\Chrome\Application\chrome.exe" --flag-switches-begin --flag-switches-end Executable Path C:\Users\gmajor\AppData\Local\Google\Chrome\Application\chrome.exe Profile Path C:\Users\gmajor\AppData\Local\Google\Chrome\User Data\Default Variations 411b6d4e-ca7d8d80 b7d3b6c2-3f4a17df d01ab0d3-ca7d8d80 3e006338-3f4a17df 1a0d11d4-2f9febdf e202a358-ca7d8d80 2b6ab552-ca7d8d80 66df3e9d-7f918788 2b6b7805-ca7d8d80 ebeb14fc-3f4a17df b7e2524c-ca7d8d80 cc20827f-ca7d8d80 8502ae4f-e1031ab5 3095aa95-3f4a17df c27fec31-b921b948 7c1bc906-f55a7974 9def365c-ca7d8d80 47e5d3db-3d47f4f4 125b7f68-898170a5 d442dfb7-ca7d8d80 9ca1387e-3f4a17df 1149accc-5c943877 4dc30737-b8a5ea08 c865fdc1-ca7d8d80 a582a1b8-ad75ce17 8ee5ed19-ca7d8d80 74658432-ca7d8d80 d0c20ec2-a9390bd0 ebbb4e0a-ca7d8d80 e56c5101-7d60f345 267255c3-f4950e99 aa011017-5d0302cf 88a387d2-ee748cef 334aa58d-3f4a17df 5e3a236d-4113a79e edbcf7c5-1cc1312c e111fcd-ca7d8d80 9b4c4257-ca7d8d80 c210447d-ca7d8d80 43f62d3b-28165b59 165e16d1-3f4a17df 3a0563a1-65222f0b 6a82868d-3f4a17df 9e5c75f1-1039a221 6872f671-991e1e1 2ca9c26b-3f4a17df 4ea303a6-ecbb250e 3d7e3f6a-2eb01455 6e6e0c7e-3f17a7d8 d92562a9-4d2fac87 fc369826-ca7d8d80 7aa46da5-c946b150 4da5ae82-91c810ef 2c1d398c-3f4a17df cc54eb06-28165b59 58a025e3-36e97b2c df072bba-ca7d8d80 4bc337ce-7b60a216 ddf77e2c-ca7d8d80 1354da85-f1a864dc 17507c76-ca7d8d80 494d8760-52325d43 f47ae82a-86f22ee5 3ac60855-486e2a9c f296190c-6754d7b7 4442aae2-d7f6b13c ed1d377-e1cc0f14 75f0f0a0-4ad60575 e2b18481-5c63917a e7e71889-4ad60575 3a8271ac-12c226 b1ceb06f-d1372334 94e68624-803f8fc4 cc73f8a1-ca7d8d80 10a311eb-ca7d8d80 8834fcca-28165b59 ea0f933d-29e3c6de c1345588-ca7d8d80 2) As you're on Windows, is it possible to download Chrome Canary ( see https://www.google.com/chrome/canary/ ), which does not replace/alter your existing Chrome installation, and test there? Chrome and Chrome Canary can run side by side on Windows, and so you can potentially test to see if it's resolved there. It works in Chrome Canary both incognito and normal It does not work in Chrome normal or icognito 3) Can you describe more about which Smartcard you're using, if you know? For example, are you using CAC, PIV, a national ID card (if so, what country), etc? DOD CaC oberthur ID One 128 v5.5a 4) Assuming it's not resolved in Canary, using Canary, can you open chrome://net-export and then, in a separate tab, attempt to login to a site that requires your smart card? You can then attach the net-export log to this bug, which will include additional diagnostics about the smartcard driver and middleware that may help us further pinpoint the issue.
,
Nov 1
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 1
Thanks! A few more follow-ups: 1) Could you include the chrome://version from Canary as well, since it's working (huzzah) 2) Can you include a chrome://net-export from both Stable and Canary attempting to login to a site? 3) Can you attach a chrome://conflicts from Stable? Trying to drill down into the possible differences here so that we can get you back to working as expected, and figure out why it broke in the first place.
,
Nov 1
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 1
1) Could you include the chrome://version from Canary as well, since it's working (huzzah) Google Chrome 72.0.3598.1 (Official Build) canary-dcheck (32-bit) (cohort: ASAN) Revision 3c9e93f2b9748f31d7be39426d3ec69c998231e7-refs/branch-heads/3598@{#2} OS Windows JavaScript V8 7.2.196 Flash 31.0.0.122 C:\Users\gmajor\AppData\Local\Google\Chrome SxS\User Data\PepperFlash\31.0.0.122\pepflashplayer.dll User Agent Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/72.0.3598.1 Safari/537.36 Command Line "C:\Users\gmajor\AppData\Local\Google\Chrome SxS\Application\chrome.exe" --flag-switches-begin --flag-switches-end Executable Path C:\Users\gmajor\AppData\Local\Google\Chrome SxS\Application\chrome.exe Profile Path C:\Users\gmajor\AppData\Local\Google\Chrome SxS\User Data\Default Variations 5e3a236d-59e286d0 2) Can you include a chrome://net-export from both Stable and Canary attempting to login to a site? Done and attached. 3) Can you attach a chrome://conflicts from Stable? Done and attached.
,
Nov 1
rsleevi@chromium.org response posted above
,
Nov 1
Odd! stable_chrome_conflicts.pdf does show "Windows Smartcard Credential Provider" getting loaded, whereas previously the failure mode was that dll didn't get load. Maybe there were two problems at the same time? The list of variations in canary_chrome-net-export-log.json and your chrome://version in Canary is surprisingly short though. I wonder why there's only one entry... just to sanity-check, that is indeed the entire content in chrome://versions, right? (They are consistent and all. I'm just confused.) Modulo confusing set of variations, I think that means neither version is running the network service though, and I don't know of other potentially relevant field trials going on. Would you be willing to run a bisect for us? This'll binary search across various pre-built revisions to find when something changed. You would need to have Python installed on your machine: https://www.python.org/downloads/release/python-2715/ The instructions are here: https://www.chromium.org/developers/bisect-builds-py This command will bisect between Chrome 69 and 70, presuming it worked in Chrome 69. This is so we can find what commit probably broke it: python bisect-builds.py -a win64 -g 576753 -b 587811 And since you mention that it now works in canary, this will bisect between Chrome 70 and the canary build it worked for you in. This is so we can find what commit probably fixed it and consider cherry-picking: python bisect-builds.py -a win64 -g 604471 -b 587811 In both cases, it'll run various revisions of Chromium. Check if each one works or not, close the browser, and type into the console whether it was good (PIN prompt worked) or bad (PIN prompt broken). Thanks!
,
Nov 5
davidben@chromium.org So, this morning Canary updated and no longer works as well. I have re-collected all the data that had been requested before. Hopefully, this sheds some light on the issue. Also, as this is a work computer, I'm not comfortable running python on it; however, I should be able to conduct the testing at home. Thanks for your help!! I've attached files for the Chrome Version with Variations, Conflicts and Net Exports.
,
Nov 5
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 5
Thanks! One of the things that would have changed with relaunching Canary is that you will have had some new experiments delivered, and it's possible that one of these experiments is causing the issue for you. Could you try modifying the Chrome Canary shortcut to include the command-line flag "--reset-variation-state"? You can see more at https://www.chromium.org/developers/how-tos/run-chromium-with-flags You'll need to close all instances of Chrome Canary first, and then launch with that flag. Go to chrome://version and copy down your variations, and then attempt to reproduce. If it works again, and chrome://variations is empty (or only one or two entries), then we know it's a feature being developed/tested that may be causing this. This doesn't really "resolve" the problem - because without further work, we won't know which feature it is or how to fix it to make sure it doesn't break you, but it'll help us come up with further steps to try and identify the issue.
,
Nov 5
rsleevi@chromium.org and davidben@chromium.org I restarted Canary with the flags prescribed, and the issue was still present. I've attached the chrome://version
,
Nov 5
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 12
Thanks! Sorry for the delays in responding - it's not intentional to take this long. I'm going to be out of the office for the next two weeks, so I'm hoping David may be able to help drive a little further. The key distinction between "Canary that worked" and "Canary that doesn't" has been the set of experiments you've been opted in to. Some of these experiments may be exposed through chrome://flags, but as a user, it's not easy to figure out and bisect which experiment it is, just from those hashes. The next steps involve identifying all the experiments you've been opted-in to, and attempting to figure out what the 'default' or 'control' group is for each of those, to replicate the original behaviour you had in the "Canary with no experiments" I'm going to tag this with Variations in case any of the team responsible for the experimentation framework has any improved suggestions for debugging and bisecting the experiments. Otherwise, it may take a few days to go through all the experiments being run and to create a set of command-line flags that can bisect them.
,
Nov 12
you can use chrome://version/?show-variations-cmd to get a command line to reproduce a build, then use this to bisect.
,
Nov 13
No worries. Just let me know what I can do to help!
,
Nov 16
The issue is already been under investigation by dev team. Hence, adding label TE-NeedsTriageHelp to push the issue out of TE-triaging bucket. Thanks...!! |
|||||||||||||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Oct 30