We are currently testing an upgrade on one of our systems from v9 to v12. In all previous versions we have set the Delta V admin password to default, we realize this is not ideal but we have quite a lot of systems and found it easier to manage this way (it saves us having to change this password when someone leaves etc). In version 12 you cant now set this to default, what do other people do to manage this password or get around the problem of issuing this password to engineers working on the system in the short term and then leaving site ?
This is a good question, and I did not even realize 12.3 enforces a non-default password until I read this.
We have clients that are implementing regular password changes of service accounts to minimize security vulnerabilities, something on the order of once per year, and are using enterprise password management software and site procedures to keep this process under control, not just for DeltaV but all manner of service accounts across different automation and business systems.
The number of people who know the DeltaVAdmin password for a particular system should be kept to a minimum; after all you only really need it when adding or replacing workstation nodes, and most of those activities should be conducted during normal business hours (except maybe for a mission critical server failure and replacement). This obviously becomes difficult if you are employing a managed services group for administration.
I don't suggest making it the same for different systems at your site, either, unless the same group of adminstrators have responsibility on those various systems.
In reply to Youssef.El-Bahtimy: