Default policy/setting to disable saving doc password to Windows Cred manager
C
Charlie B
started a topic
about 3 years ago
Hi,
Upon review of the scripting/default setting reference information, I cant see a way to disable the ability for someone to choose the "Store Password in Windows Credential manager" option.
This is due to an internal policy of not using it due to it vulnerabilities.
Does this setting exist? If not can it be added please?
Thanks
Best Answer
S
Stefan Koell
said
about 3 years ago
Hi Charlie,
right now there's no way to disable this option but I implemented a new property called PolicyDoNotAllowWindowsCredentialManager (for the RoyalApplicationSetting object) in the next minor release which can be set through our configuration system:
would that format be: "PolicyDoNotAllowWindowsCredentialManager" : true, or "PolicyDoNotAllowWindowsCredentialManager (for the RoyalApplicationSetting object)": true,
Also I also assume no harm if I pre-stage this setting now in anticipation of the update?
Thanks
C
Charlie B
said
about 3 years ago
Legend! many thanks!
Stefan Koell
said
about 3 years ago
Answer
Hi Charlie,
right now there's no way to disable this option but I implemented a new property called PolicyDoNotAllowWindowsCredentialManager (for the RoyalApplicationSetting object) in the next minor release which can be set through our configuration system:
Charlie B
Hi,
Upon review of the scripting/default setting reference information, I cant see a way to disable the ability for someone to choose the "Store Password in Windows Credential manager" option.
This is due to an internal policy of not using it due to it vulnerabilities.
Does this setting exist? If not can it be added please?
Thanks
Hi Charlie,
right now there's no way to disable this option but I implemented a new property called PolicyDoNotAllowWindowsCredentialManager (for the RoyalApplicationSetting object) in the next minor release which can be set through our configuration system:
https://docs.royalapps.com/r2021/royalts/advanced/default-settings.html
Regards,
Stefan
- Oldest First
- Popular
- Newest First
Sorted by Newest FirstStefan Koell
It would be like that in json:
as environment variable:
or registry:
And yes, pre-deploying the setting causes no harm and will be picked up as soon as the new version is installed...
1 person likes this
Charlie B
Just to check (as the documentation obviously wont show yet - https://docs.royalapps.com/r2021/scripting/objects/options/royalapplicationsetting.html#policy)
would that format be:
"PolicyDoNotAllowWindowsCredentialManager" : true,
or
"PolicyDoNotAllowWindowsCredentialManager (for the RoyalApplicationSetting object)": true,
Also I also assume no harm if I pre-stage this setting now in anticipation of the update?
Thanks
Charlie B
Legend! many thanks!
Stefan Koell
Hi Charlie,
right now there's no way to disable this option but I implemented a new property called PolicyDoNotAllowWindowsCredentialManager (for the RoyalApplicationSetting object) in the next minor release which can be set through our configuration system:
https://docs.royalapps.com/r2021/royalts/advanced/default-settings.html
Regards,
Stefan
1 person likes this
-
What happened to the forum?
-
About this Forum
-
Security Information
-
Supported Secure Gateway (SSH) ciphers
-
Why is no remote file browser in SCP available?
-
What encryption is used in the rtsz files when enabled?
-
Royal TS V4 License File
-
How to resolve RDP resolution issues in Windows 7 with high resolution screen
-
Auto Fill in web page connection
-
How to reference custom properties in tasks and templates?
See all 275 topics