Handling passwords in scheduled clones

[SBratcher]

We have a very high turnover Service Desk, and as such, have a new training class every few months, our trainers have complained since a few months after launch that the test instance being cloned from production so rarely is causing them issues in their training classes.

As such, we are working to set up a training instance that will allow for more regular clones. We want to get to the point of scheduling these clones and having the entire process be automatic so our admins don't have to interact with it at all. The only steps that we haven't gotten automated yet are updating the passwords for the mid server user and our 25+ data sources. Has anyone found a clean, secure way to have these things updated automatically post-clone?

[pavani_paluri]

Hi @SBratcher ,

Exclude the Mid server user or preserve the table with conditions on user table. For those 25+ data sources,

Create a script in Automated Fix Scripts or a Background Script that:

Runs after a clone

Store your lower-environment test passwords in System Properties or Credential Aliases, but as encrypted text.

Your script pulls those values, not hardcoded strings.

Steps:

Create a property like x_training.mid_password (type: Encrypted Text)

In the script, read that encrypted property:

var password = gs.getProperty('x_training.mid_password');

This way, your script doesn't expose the password.

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for

Kind Regards,

Pavani P