7/21/2011 7:13:15 PM
 Blake P Posts: 19
|
First off, we are a Managed Services Provider with about 30 employees, we have good documentation, but we are looking to enforce a few things to keep our DB Admins from having to constantly clean up newly added records. The documentation is only as good as the minion following it ;P
So im looking at this as a feature request. We have a problem with people within our company using the wrong template when putting in new records. What I would like to do is have a regex on the "username" field on a few of our templates that would prevent the record from being added if that field contained "administrator" or a few other configurable common options unique to our company.
Would also like to do the same for our "Remote Access" template in the IP Address field, to make sure that it is a valid IP address being entered.
I have about 10 different examples where this would be a great feature to ensure documentation standards are met within our company.
Anyone else agree or have any ideas on how I could do this currently?
Thanks!
|
|
|
0
• link
|
7/22/2011 11:16:32 AM
 Ben Posts: 94
|
Hi Blake,
Thanks for the suggestion. I've added this as a feature request for prioritization into the roadmap. Secret Server does support default values for a field, which you can specify on the template. Which would force users to choose specific values when creating a Secret.
-- Thycotic Development Team
|
|
|
0
• link
|
7/22/2011 12:49:54 PM
 Blake P Posts: 19
|
Oh yes, and that has helped us extensively with making sure that documentation standards are followed, however the fields that there can be some differences in we would like to enforce people to use the right account. I did submit a few of the templates that we have created for some of our more complex records over the past few days, and there will be more to come as I get more of them cleaned up and fully utilizing the dropdowns.
For all networks that we support entirely we have an MSPService account which we would like to do a regex or something to prevent the record from being saved if the username field says administrator or MSPService or something along these lines.
As always thank you guys so much for your great support and listening to the customers!
|
|
|
0
• link
|