Description of problem:
I would like kickstart and cron scripts to submit Custom Info values, so I can search on those fields and feed them back into config files. The current rhn-custom-info requires a user/password for all changes, making it insecure to embed in scripts.
Creating a Custom System Info key includes a toggle for "Allow changes from client." The rhn-custom-info includes a '--quiet' or similar flag that will exit abnormally, rather than prompt for a password, if the client tries to change a value it isn't allowed to change.
Allowing an arbitrary client to change or even create custom system values
would go against the security model used in Spacewalk: you need to have
appropriate permissions to manipulate the system data on the server
(organization admin for example).
I can see how one could benefit from being able to do the data changes
without authentication (or authorization), but the functionality could
also be abused in the same manner.
Spacewalk's API provides several routines to manipulate the system
custom info. May I suggest to export the data from client to a system
where it is safe to store the password and change the system info
Terribly sorry, I'm gonna have to close this RFE.