Maximo Open Forum

View Only

Back to discussions

Expand all | Collapse all

MAS Saas User Sync errors

Bernardo Ferreira4 days ago

Hi, I have already opened a case, but I am also trying to get some input from the community. We have ...

Clyde Waters3 days ago

It's difficult to say whether this is the exact same issue, but we have encountered similar sync error ...

1. MAS Saas User Sync errors

Like
Bernardo Ferreira
Posted 4 days ago

Reply Reply Privately
Hi,

I have already opened a case, but I am also trying to get some input from the community.

We have a MAS SaaS environment where, obviously, we do not manage most of the background infrastructure. We are experiencing some issues with user synchronization that do not seem to follow any specific pattern. Only a few users consistently get synchronization errors.

The errors shown during the sync are:

In Suite -> Security -> Users, when opening a user with a sync error:

BMXLM0504E - HTTP Response Code 403:

<html>

<head><title>403 Forbidden</title></head>

<body>

<center><h1>403 Forbidden</h1></center>

<hr><center>nginx</center>

</body>

</html>

In the user sync menu:

AIUI1101E: Internal user agent error.

Details: [main 141440] synched: status_code: 400 r.text Error 400: system#sysncerrorsyncfrommas

Has anyone experienced this issue or found the root cause?

Thank you.

#MaximoApplicationSuite
#MaximoUserGroups

------------------------------
Bernardo Ferreira
Sofitnsa
------------------------------
2. RE: MAS Saas User Sync errors

Like
Clyde Waters
Posted 3 days ago

Reply Reply Privately
It's difficult to say whether this is the exact same issue, but we have encountered similar sync error messages previously. In our case, the root cause was not related to the user records themselves, but rather a problem with the internal communication between Manage and the Internal API. Manage-to-Internal API requests were failing with HTTP 403 responses due to an issue with the authentication used for service-to-service communication.

The issue was ultimately resolved by deleting the affected secret and restarting the Internal API service. Once the secret was recreated and the service restarted, user sync operations completed successfully.

If you have access to the Manage and Internal API logs, it may be worth checking for broader 403 errors between MAS components.

------------------------------
Clyde Waters
Naviam
------------------------------