Record producer submission by an unauthenticated user returns HTTP 401Issue A record producer is configured to be visible to public users. An unauthenticated user can open and complete the form, but submitting it fails with an HTTP 401 response. No record is created in the target table. The same record producer can be submitted by authenticated users, including a user assigned only the public role. Release Not release specific Cause Displaying a record producer publicly does not make its submission endpoint available to an unauthenticated session. The portal submits the record producer through the out-of-box submit_producer REST resource. That resource requires authentication, so submission from a truly unauthenticated session returns HTTP 401. This behavior is separate from: Create or write ACLs on the target tablePublic visibility of the record producerPublic availability of its variablesCatalog UI policiesAssigning the public role to an authenticated user An authenticated user with the public role is not equivalent to an unauthenticated guest session. Resolution Unauthenticated submission of a record producer is not supported through the out-of-box submit_producer resource. Keep Requires authentication enabled on the out-of-box submit_producer REST resource.Do not modify the out-of-box resource to bypass authentication for an individual record producer.Require users to authenticate before submitting the record producer.If unauthenticated submission is a business requirement, implement a separately designed custom solution through the appropriate development or implementation channel.Validate the custom solution’s authentication model, input handling, and security controls before deployment. Disabling authentication on the out-of-box resource is not an appropriate record-producer-specific workaround because the resource is shared.