After Clone Prod to dev - facing (MID Server )Basic authentication failed for user: mid_acc

[Baskarank053386]

In servicenow after clone the prod to dev instance it was facing the mid server (Basic authentication failed for user: mid_acc ) and continously tiggered the error in log table . And  mid_acc  in this user not in sys_user table after cloning the instance and how to resolve this issue?

[Kieran Anson]

You'll have to recreate the user, you'll then need to update the MID server config.xml with the new username and password. Lastly the MID service will need restarting to take the new configuration

[Baskarank053386]

ok, now Create the user same user in MID Server Logged User (mid_acc) in user table and add roles but that user was automatically logged out feild is checked .  why?

[Kieran Anson]

"automatically logged out" field - I'm not aware of such a field OOB. Are you referring to locked out? Is this a custom field?

[Anand Kumar P]

Hi @Baskarank053386 ,

The issue occurs because the MID Server user account (‘mid_acc’) from the production instance was not copied during the cloning process. As a result, the MID Server in the development instance tries to authenticate with a missing user, causing authentication failures.

You have to edit the config.xml file go through kb and restart the midserver-https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0597574

If my response helped, please mark it as the accepted solution ✅ and give a thumbs up👍.
Thanks,
Anand