Mid server user getting Locked out automatically
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-10-2024 03:32 AM
Hi Everyone,
We don't know why the mid server user profile in our non-prod instance is getting inactive and locked out after every minute, the mid server status is fluctuating after the password being rotated in config file and user table. We have tired making the account active and removed the check in from lock out but again in sometime he gets locked out. The account is active in the active directory as well everything is perfect according to the profile. The password entered in both the ends have been verified but still the user account get locked automatically.
Do anyone faced the same issue. please let us know what needs to be done in this case.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-10-2024 05:18 AM
Hi @Anitha
You can refer below posts and give it a try :
https://www.servicenow.com/community/itom-forum/mid-server-user-account-locked-out/m-p/967363
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0597574
Thanks and Regards
Amit Verma
Please mark this response as correct and helpful if it assisted you with your question.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-11-2024 11:49 PM
Is it another MID server trying to log in with that User and the wrong password?
You can check the event logs for incorrect password attempts.
Turn off all of the MID servers that use it, check if there are still incorrect password attempts.
If YES - Another MID could be using the password so turn them all off nd one by one, turn them on and check the MID Server Logs, you will quickly work out which one has the wrong password. If none do, then something else is trying to log in with the MID Server account.
If NO - then your MID Server is not getting the new password correctly or something else is trying to use the MID account with the wrong password.
If you cannot work out who is trying to log in with the MID Server account, then change the username and update anything that needs to use it.