Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Hudu People sync issues #3639

Open
3 tasks done
HappyEarthDay opened this issue Feb 13, 2025 · 1 comment
Open
3 tasks done

[Bug]: Hudu People sync issues #3639

HappyEarthDay opened this issue Feb 13, 2025 · 1 comment
Labels
bug Something isn't working unconfirmed-by-user

Comments

@HappyEarthDay
Copy link

Required confirmations before submitting

  • I can reproduce this issue on the latest released versions of both CIPP and CIPP-API.
  • I have searched existing issues (both open and closed) to avoid duplicates.
  • I am not requesting general support; this is an actual bug report.

Issue Description

Issue Details:

  • For at least four clients, the integration is updating the same Hudu asset for all M365 users in a tenant, instead of creating or updating individual People assets. In those cases, only one People asset continuously gets overwritten with different user information.
  • Most tenants appear to be unaffected, but four impacted tenants have been identified so far.
  • It looks like the newest clients have been impacted. All clients have Business Premium licensing.
  • I tried to reset the Hudu integration by removing all data from the CIPP integration screens, including mappings, then disabling it. Then I input all the information again and re-did the mappings. The sync behavior occurs.
  • I played with the number of existing/manually created People assets for the problematic clients. When there are no People assets, no assets are created. When there is one or more, only one People asset is updated, the rest are ignored.
  • All Magic Dashes are displaying correct information, and Devices sync is working as expected.
  • This Hudu instance is behind a Cloudflare tunnel and proxy but not Zero Trust (open to public). No service key is needed for auth and all other integrations and custom automations are working correctly.

Possible Causes:

Expected Behavior:
Each licensed M365 user in a tenant should sync to their own individual People asset in Hudu, rather than all users being written into one asset.

Examples & Logs
Even for the clients that are working, I am getting error in the Hudu sync logs: User brian.REDACTED.life#EXT#@REDACTED .onmicrosoft.com: Multiple Users Matched to email address in Hudu: (REDACTED Fax, Ketsia REDACTED , Social Media, Elizabeth REDACTED , REDACTED Admin (No Reply), Esteban REDACTED , brian.REDACTED , Edie REDACTED , Christina REDACTED , Nancy REDACTED , Sydney REDACTED , Dutch REDACTED , Jay REDACTED , REDACTED Distribution, REDACTED Donor, REDACTED Clinic, Alex REDACTED - 3240, 3242, 3243, 3239, 3241, 2414, 2410, 2413, 2412, 2418, 2419, 2417, 2416, 3744, 3745, 3746, 3238) Even though I get this error message in the CIPP logs, I can see that all of the users listed are actually getting updated in Hudu, and they are not displayed in the CIPP logs as being updated, only in the errors log.

Example of a problematic client, where the email address gets updated on a single People asset for each licensed user in the tenant:
Image

Example of Hudu logs that show the single People asset being updated by CIPP multiple times:
Image

My People asset, which I created using the built-in template, then modified for my own purposes:
Image

Environment Type

Sponsored (paying) user

Front End Version

2.7.1

Back End Version

2.7.1

Relevant Logs / Stack Trace


@HappyEarthDay HappyEarthDay added bug Something isn't working unconfirmed-by-user labels Feb 13, 2025
Copy link

Thank you for reporting a potential bug. If you would like to work on this bug, please comment:

I would like to work on this please!

Thank you for helping us maintain the project!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working unconfirmed-by-user
Projects
None yet
Development

No branches or pull requests

1 participant