Issue with Attribute Sync in Entra ID – HTTP 400 Error

Identity Security Cloud (ISC) ISC Discussion and Questions
, ,
1

Hi Team,

I’m encountering an issue with Attribute Sync for the attribute in the Entra ID application.

I have successfully enabled attribute sync, and during account creation, the value is correctly passed and provisioned via the provisioning plan.

However, when attribute sync attempts to update, it fails with the following error:

less

[ConnectorError] AxiosError: Request failed with status code 400 (requestId: ec877aa8-1650-44b3-b846-df95f75fcb1f)

Has anyone experienced a similar issue or can provide guidance on what might be causing the 400 Bad Request during attribute sync?

Any help or suggestions would be greatly appreciated.

2

Hi Harsh,

sail conn logs tail
3

No @vbdm , It is Department normal attribute.

4

Hi @hkhandale,

  1. Is the issue happening with all users and all attributes.?

  2. If it’s a synced attribute (synced from AD in a hybrid setup) Entra would reject the updates.

  3. The API call may also fail if it is a guest user.

  4. Also, sending a null value can also result in a failure.

5

It is showing me lots of Modify account Failed while aggregation Due to Department Sync

6

I am syncing Workday attribute on Entra, and it is prod and only single attribute is enabled

7

Yes it is guest user, but it is working in Dev Tenant

8

Previous value is not a null still it is getting Failed

9

After reading all your messages, this could be something that Entra ID is rejecting. To know the exact reason, if I were you, I would use cli tool, connect to Prod and then tail the logs, as mentioned here: Connectors | SailPoint Developer Community

You will see something like this(outlined text):

image
image1050×357 61.1 KB

Further, with Entra ID, I have seen that sandbox and prod connectors behave differently even when they are on the same version.

10

As I saw the events, few are getting passed and others are getting failed
Not able to understand this behaviour

11

Hey Jesvin,

Why would the API call fail if it is a Guest User? Are Guest Users treated differently then Members when it comes to an Attribute Sync?

12

As I check for some guest user it is getting passed and for rest getting failed with mentioned error

I tried to enable Sync for other attribute as well and getting same issue

13

That’s interesting. Would you mind sharing your logs

I’d like to see how some guest users are getting passed and some others have the mentioned error

14

Yes sure,

image
image800×291 60.1 KB

for Passed

image
image418×648 41.4 KB

for Failed

[ConnectorError] AxiosError: Request failed with status code 400 (requestId: ec877aa8-1650-44b3-b846-df95f75fcb1f)

15

Hi @hkhandale

were you able to solve this?

16

No resolution yet — the same issue persists :cry:

19

Okay have you tried to setup the CLI. Since this is SaaS connector, we should find some useful input.

20

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.