Chef cookbook and knife plugin projects

**_Authenticating to the tomcat7 manager application using client SSL_** I would like to have a tomcat cookbook called "tomcat-auth" to deploy the manager application, but modify it to support SSL client authentication from admin-users. **_Authenticating to the tomcat7 manager application using openid_** similar to the above requirement, I would be interested in having a cookbook which configured tomcat to do openid authentication **_Plugin for knife "install", which is similar to the "yum install" type paradigm_** so to develop a knife plugin, which allows an administrator to run a cookbook recipe in an unmanaged way. The cookbook would be from the chef server, but would be run in the context of the local chef-client user. The use case is that a developer would be able to install "tomcat" cookbook to some node, but be able to make changes such as to files "[login to view URL]" and not have chef "clobber" the changes required for debugging etc. ## Deliverables This is a fixed hours project to capture some work done on 2 related projects I would like to contract a Chef professional to customize the existing community tomcat cookbook for the apache tomcat 7 release; **_Authenticating to the tomcat7 manager application using client SSL_** I would like to have a tomcat7 (and a bonus would be compatible with tomcat6) to deploy the manager application, but modify it to support SSL client authentication. **_Authenticating to the tomcat7 manager application using openid_** similar to the above requirement, I would be interested in having a cookbook which configured tomcat to do openid authentication _**SSL auth**_ basically I have a some tomcat servers, and users issued with personal SSL client certificates on USB tokens which are available to authenticate to the server, which are used to access the corporate intranet. I am looking for a chef cookbook to deploy the manager app to wrap up that functionality, so the recipe will deploy the manager app, and add a [login to view URL] that requires the user to provide a client SSL cert that validates against a particular CA cert. _**OpenID**_ similar to the above requirement, I would be interested in having a cookbook which configured tomcat to do openid authentication This would invoved the following steps... 1//Tomcat Server configuration with chef using the providers ( 20 hours max ) 1. BASIC - [login to view URL] 2. CLIENT-CERT - [login to view URL] 3. OpenID : use of one of many providers For openId you need the tcat xml file to change like this ------ secured resources /web/* * OPENID /[login to view URL] /[login to view URL] === EDIT === this was the old description, has been updated to the above [login to view URL] Out main platform is Centos 6 but there is no package currently for tomcat7 in the distro repos, hence the requirement to package for chef. requirements; run tomcat as tomcat user install /etc/init.d/tomcat script compatible with the community java cookbook work with oracle JDK or openJDK Here are some notes on installing tomcat 7 into CentOS [login to view URL] [login to view URL] [login to view URL] There is another tomcat7 cookbook that has AL20 licensing that can be used as a basis; [login to view URL] [login to view URL] [login to view URL] Often on a developer box, I'd like to deploy a cookbook recipe, some arbitrary cookbook recipe using the chef server (not chef solo), but leave it unmanaged so the developers can make changes and not get clobbered by chef trying to change things back. It would work something like $ knife install "recipe[myrecipe]" and knife would use shef, or otherwise to install the recipe locally. So Knife plugin "install " for unmanaged recipies : Use the Shef API to bypass all chef mechanism