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

Unable to set externalId attribute on outgoing responses #74

Closed
sleelin opened this issue Feb 24, 2025 · 0 comments · Fixed by #76
Closed

Unable to set externalId attribute on outgoing responses #74

sleelin opened this issue Feb 24, 2025 · 0 comments · Fixed by #76
Assignees
Labels
bug Something isn't working
Milestone

Comments

@sleelin
Copy link
Collaborator

sleelin commented Feb 24, 2025

Currently, the externalId common attribute is marked with a direction of "in". This was intended to ensure it is only ever set in incoming requests, but also means it is stripped from outgoing responses. This appears to be causing Microsoft Entra ID to re-sync every user, as it is using externalId as a sync "anchor".

Expected Behavior

The externalId attribute should not be stripped from outgoing responses.

Actual Behavior

The externalId attribute is stripped from outgoing responses, despite being set.

Steps To Reproduce

  1. Include an externalId property in the return value of any egress handler
  2. Observe that it has been removed in the outbound message
@sleelin sleelin added the bug Something isn't working label Feb 24, 2025
@sleelin sleelin added this to the 1.3.4 milestone Feb 24, 2025
@sleelin sleelin self-assigned this Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

Successfully merging a pull request may close this issue.

1 participant