MID Server not operational (status: Down), possibly due to recent clone. - how to resolve?

[Baskarank]

After Clone prod to dev that MID Server logged "mid_acc_rdev" user was not in user table. So i was create the user same as user id "mid_acc_rdev" , add the mid server role and reset the password same as config.xml file and Restart the server and validate the MID Server but still server is down and that user was some time lockout automatically.

how to resolve this issue?

Logs: 

ExternalAuth: provider_user_map is de-activated for user:83c994ee3b7ada5011da22aaa4e45a48 ➚

User mid_acc_rdev locked out due to too many invalid login attempts

Basic authentication failed for user: mid_acc_rdev

Auto-unlocking user MID Server

[ZacharyKenyon]

The mid.instance.password parameter in config.xml has the parameter:  secure="true" and the value would be something like "ENCv2[<encrypted password>]"

This means that the password is encrypted in the config.xml, so you can't just copy it out of there and use it in the instance.  Instead, you should set the password in the instance, and then paste that into the value for mid.instance.password (replacing the entire string including ENCv2 and the brackets).

[tdevine1]

The issue might be with the password, when you start the MID Server it encrypts the password. So the value that you see is not the true password. You will need to:
1. Create a new password in ServiceNow

2. Stop the MID Server service from running on the VM

3. Edit the Config.xml file

4. Replace the current current password with the one generated by ServiceNow

5. Save the file

6. Restart the MID Server service. (This should connect and encrypt the password in the XML file again)

[Baskarank]

Thank you , Now status is UP but 2 unresolved issue in the tab 

MID Server Issue Tab:

-------------------------

1.Could not decrypt file discovery whitelist after sync

2.MID Server encryption keys do not match and are no longer valid. To restore proper functionality, invalidate and re-validate the MID Server.