Bug #12488
closedNew Feature #11078: Windows Certificate Management
Task #12485: Windows Certificate Management feature related Issues
Certificates did not removed when a another policy applied
100%
Description
Environment details
630 staging server
Prerequisites
windows device
created windows certificate manager policy
Description
Issues:
Result is shown here: [1]
Need to fix line 6, 8, 12, 13
Result
[1]
Files
Updated by Ruwin Dissanayake 8 days ago
- File Screenshot from 2025-02-12 17-30-29.png Screenshot from 2025-02-12 17-30-29.png added
- Status changed from New to QA
- % Done changed from 40 to 100
When certificate is added to device wise for untrusted store and trusted publisher store it automatically gets added to the respective user certificate stores also, that's the intended behaviour for those mentioned certificate stores. To test that manually installed the same certificate to the device untrusted store and it automatically added to the user untrusted store as well and when revoking once the certificate is deleted from the device store it automatically gets deleted from the user store. For the intermediate store with the microsoft updates they have updated the certificate stores and now they are pushing to use the intermediate store instead of the trusted root store in newer windows machines as both of them are doing the same task [2].
Updated by Arshana Atapattu 7 days ago
- Status changed from QA to Closed
Ruwin Dissanayake wrote in #note-2:
When certificate is added to device wise for untrusted store and trusted publisher store it automatically gets added to the respective user certificate stores also, that's the intended behaviour for those mentioned certificate stores. To test that manually installed the same certificate to the device untrusted store and it automatically added to the user untrusted store as well and when revoking once the certificate is deleted from the device store it automatically gets deleted from the user store. For the intermediate store with the microsoft updates they have updated the certificate stores and now they are pushing to use the intermediate store instead of the trusted root store in newer windows machines as both of them are doing the same task [2].
Closing with the given explanation.