AutoSelectCertificateForUrls with SUBJECT CN
Reported by
erdanzie...@googlemail.com,
Apr 3 2017
|
||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36
Steps to reproduce the problem:
1. {"pattern":"https://server.com/customer_code/","filter":{"ISSUER":{"CN":"issuer_code"}}} works fine
2. {"pattern":"https://server.com/customer_code/","filter":{"SUBJECT":{"CN":"customer_code"}}} doesn't work
What is the expected behavior?
It should search and use the client certificate automatically which has SUBJECT CN => customer_code.
What went wrong?
SUBJECT CN seems to be ignored. Only ISSUER CN works.
Did this work before? No
Chrome version: 57.0.2987.133 Channel: stable
OS Version: OS X 10.12.3
Flash Version:
We are creating client certificates for all our customer. Because all client certificates has the same ISSUER CN we would like to select a client certificate automatically by using the SUBJECT CN. Maybe SUBJECT isn't the right word?
,
Apr 3 2017
Tagging as Feature Request.
,
Apr 4 2017
Untriaged it to get addressed further by the respective component owners.
,
Apr 4 2017
Removing component; it's an Enterprise feature request.
,
Apr 5 2017
,
Apr 7 2017
David for prioritization.
,
Apr 25 2017
,
Jun 5 2017
,
Sep 6 2017
Its very time consuming, nearly unusable. The more certificates we install the longer it takes to find the right one. Specially because we need to do this multiple times per day. A simple alphabetical sorting would already save so much time. May i develop this? Please provide me the source files for the "Select a certificate" window. Thanks a lot, Marcus
,
Mar 26 2018
FYI, I have: https://chromium-review.googlesource.com/#/c/chromium/src/+/980832 out for review that would add ability to match against Subject CN as well as allowing wildcards (* and ?) in the issuer and subject CN fields.
,
Apr 11 2018
,
Apr 12 2018
That's awesome!! I check this asap and get back to you with my feedback. Thanks a lot, appreciate your effort.
,
Apr 19 2018
It appears that solution has been rejected and the referenced bug: https://bugs.chromium.org/p/chromium/issues/detail?id=824940 isn't public. Is there anything you can share on the progress of this issue?
,
May 10 2018
Any progress on this?
,
Jun 11 2018
Greetings, is there any progress on this? Would greatly appreciate it. Thanks.
,
Jul 13
I wonder if this will ever be implemented :(
,
Aug 23
,
Sep 15
Any progress on this? This is not just enterprise feature, even individual users like me using SSO certificates need this feature.
,
Sep 18
,
Sep 19
,
Nov 12
I requested this over a year now... :-( Any update are highly appreciated.
,
Nov 13
,
Dec 20
,
Dec 21
I fixed bug 824940 back in May, it added support to having mutliple filters for the same pattern. Before, any new filter would override the previous filter for that pattern. It doesn't fix the issue with filtering by Subject CN though. I'm not too familiar as to why we're not allowing filtering by subject CN yet (+cc: pmarko@) or why exactly the previously mentioned CL (https://chromium-review.googlesource.com/c/chromium/src/+/980832/2) was rejected (+cc: rsleevi@). @rsleevi: could you elaborate what you mean by "* and ? suddenly become glob characters"? To me it seems like we would just allow filtering by subject.CN with that CL. I'm happy to follow up with that mentioned CL and supporting tests if we decide to go forward with this.
,
Dec 21
see previous comment
,
Dec 21
That CL introduced two separate behaviours - wildcard/globbing support and subject CN support. I expressed particular concern with the former behaviour. pmarko@ had been looking at unifying the matching behaviour (see Issue 905994) that would have avoided the globbing and allow filtering for both Subject and Issuer on CN, L, O, OU. Comment #9 on that bug seems like the best solution. |
||||||||||||||||
►
Sign in to add a comment |
||||||||||||||||
Comment 1 by erdanzie...@googlemail.com
, Apr 3 2017