Integration account is automatically failing after few hours
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday - last edited yesterday
- Hi all
I am facing issue with my Integration account. It Start failing with error unauthorized failed after few hours automatically with same credentials while calling API through postman in UAT instance. I reseted password, exported the same account from dev instance to the uat instance in which I am facing this issue, but it worked fine for some time but again start throughing same error after few hours on the same day. I checked even the account is not locked.
Same account is not having issue in dev instance.
Any idea what exactly is the issue and how to fix it?
Thanks in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
8 hours ago
Hi Savreet Singh K,
Your integration account is getting locked out in UAT due to repeated failed login attempts from your own REST calls (logged as "Guest" in user audit). UAT has stricter security/lockout policy than Dev, so it triggers after a few hours. Password reset or export from Dev only gives temporary relief.
Root cause
- Bad/misconfigured Basic Auth in REST Message or script (common bug: using both Basic profile + manual header, or stale creds).
- Each failed attempt counts toward glide.login.lockout.threshold (default 5). After that, API access blocks even if user shows not locked.
Immediate steps in UAT:
- Check User Audit (sys_audit) or Login History for your integration user look for multiple "failed login" entries.
- In your Outbound REST Message:
- Set Authentication type = Basic
- OR remove Basic and manually add header: Authorization: Basic <base64(username:password)>
- Do not mix both.
- Reset the integration user password again.
- Test the exact call from REST Message > Test .
- Run your job/scheduled script and monitor.
Permanent solution:
Switch to OAuth 2.0 Client Credentials for integrations Basic Auth is legacy and prone to this exact issue.
