On 01/12/10 00:41, Nick Lewis wrote: > It would be nice to have a simple alternate authentication system (even > a "none" system like we tried to write) which would help motivate these > changes. That would also help figure out the API, since other > authentication systems may not necessarily have the same logical setup > steps that SSL does.
FYI, I pushed to my github repository[1] an HTTP basic auth plugin system. The system needs an htpasswd file server side with an entry per node (where the username is the node fqdn). The client can set its username and password through the settings sub-system. This is only a POC (there's no tests) of another system, I won't advise anyone to run this in production, and in any case I can't be held responsible for anything that could result from running this code :-D For rack/mongrel, the htpasswd file needs to be configured in apache/nginx/whatever you use. For webrick the plugin takes care of loading it with the http_basic_htpasswd setting. That'll give you another opportunity to review this patch :) I'll add more tests when I'll have some time (ie the AuthHTTPWrapper system). Thanks, [1]: https://github.com/masterzen/puppet/tree/feature/master/3958 -- Brice Figureau My Blog: http://www.masterzen.fr/ -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
