VS Code Zowe Extension Triggers keyring.win32-x64-msvc.node Even with "zowe.security.secureCredentialsEnabled": false Coded

[CPaceBMI]

Hopefully someone can help. When my VS Code Zowe Extension Upgraded from 3.2 to 3.3, the Zowe Extension is trying to launch keyring.win32-x64-msvc.node even though I have "zowe.security.secureCredentialsEnabled": false coded in my settings.json.

I had to already remove all the secure: [ ] entries from the profile to get it back up and running, which is fine as I found that noted, but how can I get it to stop trying to trigger the keyring? This is not approved by our security policy, so it is annoying to have to acknowledge the security notification every time Zowe is started/restarted?

Thanks,

Craig

[CPaceBMI]

Anybody out there got any suggestions on this?

[traeok]

Hi @CPaceBMI, this is the first time I've heard of the keyring binaries loading when the secure credential manager is disabled, but that's definitely something we should avoid doing. I can run some tests in my environment to try to reproduce. In the meantime, can you clarify whether the setting CredentialManager is set to false in the .zowe/settings/imperative.json file? The setting is located in the overrides section.

[CPaceBMI]

@traeok thank you for the response and yes it is set to false as below, which is my only entry imperative.json file.

{
"overrides": {
"CredentialManager": false
}
}

[CPaceBMI]

@traeok: Just wondering if you might have any other suggestions or anyone else out there?