3/14/2012 3:35:36 PM
 Jason C Posts: 1
|
In my previous environment I beleve we had the ability to give users viewable rights for secrets in folders they did not have access to the passwords. Can someone let me know how I can tweak this? I have already reviewed the doublelock, Request Access and launcher options with tech support and this is not the solution I was looking for. one of the reasons for this request is trying to prevent secrets being entered multiple times.
|
|
|
0
• link
|
3/14/2012 4:54:32 PM
 David Posts: 81
|
Hello Jason,
Just to clarify, do you want users to be able to see the names of Secrets they can't access?
Currently, this is not possible to do. I will add this as a feature request.
|
|
|
0
• link
|
4/4/2012 3:00:30 AM
 Peter C Posts: 28
|
We also need something similar. We install our servers automatically and want to create a Secret according to our Name Standard (SecretName Name Standard). When a server is re-installed, the secret would be created a second time - thats not so good. An idea would be to make the SecretName a unique field across all secrets. So when i try to create a secret with the name Server1_LocalAdmin1 when this name is already used i get an useful error.
Is there a way to initiate a SecretServer password change via Powershell/Webservices? This would also be needed.
Thanks, Peter
|
|
|
0
• link
|
4/4/2012 10:52:41 AM
 Ben Posts: 94
|
Hi Peter,
Thanks for the suggestions. In the latest version of Secret Server there is a new web service method to expire a Secret. This will initiate a password change if Auto Change is enabled on the Secret.
Ben
-- Thycotic Development Team
|
|
|
0
• link
|