-
Notifications
You must be signed in to change notification settings - Fork 27
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
Object registration plugin expects Auth Attribute Path when "update existing object" is not set. #5034
Labels
Milestone
Comments
vaszig
added a commit
that referenced
this issue
Jan 30, 2025
vaszig
added a commit
that referenced
this issue
Jan 30, 2025
10 tasks
vaszig
added a commit
that referenced
this issue
Jan 30, 2025
vaszig
added a commit
that referenced
this issue
Jan 30, 2025
vaszig
added a commit
that referenced
this issue
Jan 30, 2025
vaszig
added a commit
that referenced
this issue
Jan 30, 2025
sergei-maertens
added a commit
that referenced
this issue
Jan 31, 2025
…ng-object-in-Objects-api-expects-authattribute [#5034] Fix object ownership in Objects API
sergei-maertens
pushed a commit
that referenced
this issue
Jan 31, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Product versie / Product version
3.0.1
Customer reference
DH
Omschrijf het probleem / Describe the bug
Sentry: 391347
When a form had objects API prefill set, but registration is set to not update the same object - instead create a different type of object. The assertion of Auth Attribute Path should be skipped.
Do not update setting

prefill object:

The text was updated successfully, but these errors were encountered: