Today you have to provide credentials to create a new batch. At the F2F in January 2024 we talked about dropping this restriction. Instead anonymous users should be allowed create batches up to a configurable maximum size.
Approach 1: Make user batch_create credential parameters optional
Make batch_create authorize batch creation for anonymous users, and
add a configuration property for maximum batch size that only applies to anonymous users.
Remove the user credential parameters from the batch_create method,
add a configuration property for maximum batch size that applies to all users,
remove the (now redundant) RPCAPI.enable_batch_create config parameter, and
add a configuration document for using the batch function.
Clean up
Remove the user_create method, and
remove the RPCAPI.enable_user_create config parameter,
sever the relation between RPCAPI.enable_batch_create and RPCAPI.enable_add_batch_job configuration properties, making the former into a proper property of its own, and
change the default value of RPCAPI.enable_batch_create to false.
Alternatives
Keep the RPCAPI.enable_batch_create config parameter.
Today you have to provide credentials to create a new batch. At the F2F in January 2024 we talked about dropping this restriction. Instead anonymous users should be allowed create batches up to a configurable maximum size.
Approach 1: Make user batch_create credential parameters optional
Approach 2: Remove batch_create credential parameters
Clean up
Alternatives
Stabilization
Tracking issue
Affected interfaces
Additions:
Additional affected interfaces for approach 2
Incompatibly changed:
Dependencies
Dependencies for approach 1
Dependencies for approach 2
Overlapping proposals