KB1443041 The Opt-in instructions just don't work

NStefanisko
Tera Expert

WRT: KB1443041
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1443041

 

I'm in my Vancouver instance, I am elevated to security_admin, I should have The Power of Greyskull at this point.


I'm trying to follow the steps to enable 3DES deprecation, but the steps are just wrong.
* I wanted to make sure I have the KMF plugin (pretty sure I do) , but when I go to plugins and search for KMF, nothing shows up. Fine, I'll assume I have it.
* When I go to system properties, it gives me a nice UI, but none of the properties listed show up. Fine I'll force the table view, oh there they are. And the are set correctly. Next I'm supposed to: Set the “Instance_level_glide_encrypter” KMF password2 sub-module MAPs to track. Where? Well, the other properties were already set, so I'm going to assume this one is too, next step.
* "Go to the left navigator in your instance and go to this module > System Security -> High Security Settings -> Security Compliance -> Password2 3DES deprecation"  What left navigator, this is Next Experience, there's an "All" maybe they mean that. I can get as far as "High Security Settings", it's an end point. That takes me to "High Security Properties", and inside that there is no "Security Compliance", there isn't even a "Security Compliance" in the navigator.

 

Now I give up. How am I supposed to enable the deprecation when the instructions to do so are completely wrong?

1 ACCEPTED SOLUTION

NStefanisko
Tera Expert

Yep, that was the problem. We had a pre-release version that did not include all the modules necessary to run the test suite for this KB. Updating to the latest patch level fixed that.

View solution in original post

3 REPLIES 3

Bert_c1
Kilo Patron

Hi,

 

I would recommend creating a Support Case for this. If someone else here doesn't describe how to do what you want.

Turns out we have a Pre-Release Vancouver Instance. We are going to patch it up first, then if it is still a problem, I'll escalate.

NStefanisko
Tera Expert

Yep, that was the problem. We had a pre-release version that did not include all the modules necessary to run the test suite for this KB. Updating to the latest patch level fixed that.