8/28/2012 10:07:38 PM
 Nick S Posts: 25
|
It would be a cool addition to the tool if it could support "magic words" or "tokens" within the secret name to auto-populate it with relevant information from within the template.
Users could use tokens (ex "%1") or perhaps magic words (ex "%username%") to populate the secret name with values from within the template.
Consider the following AD secret:
Domain: LOCAL Username: srvAdmin Password: **** Notes: Test Account
A tokenized request may look something like Secret Name: %1\%2 (%4)
and would render like Secret Name: LOCAL\srvAdmin (Test Account)
A magic word implementation may look something like Secret Name: %domain%\%username% (%notes%)
Would still render like Secret Name: LOCAL\srvAdmin (Test Account)
This could help with consistency and reduce the redundant typing folks may do (I bet 9 out of 10 secret names probably contain the username).
Additional feature request: Don't just check the "Secret Name" for duplicates, also check the "Username" field.
|
|
|
0
• link
|
8/29/2012 11:27:43 AM
 Joshua C Administrator Posts: 75
|
Hello Nick,
Thank you, those feature have been requested before and we have them on our roadmap. I will add your name as a interested party.
Kind Regards, Joshua Conroy
-- Thycotic Support Engineer
|
|
|
0
• link
|
9/11/2012 5:12:50 AM
 Peter C Posts: 28
|
You already have this "Name Pattern Checking" for each secret Template. Would be really nice, if a user enters some Values and the Secret Name is then created automatically. We're still fighting duplicate old (before you introduced the Feature) secrets because users didn't use our Standards. Regards, Peter Cermak
|
|
|
0
• link
|
9/11/2012 1:23:15 PM
 Joshua C Administrator Posts: 75
|
Hello Peter,
Thank you for feedback, I will add this to our list of feature requests.
Kind Regards, Joshua Conroy
-- Thycotic Support Engineer
|
|
|
0
• link
|