How you use XConfToolTask depends on how you are building your Cocoon webapp. We build a vanilla cocoon war file and then build our stuff separately. We then unwar cocoon's war into a build directory, lay our stuff on top, and then use XConfToolTask to patch cocoon.xconf as necessary. We have our own roles file.
We also due authorization. I created a PermissionSelector that, based on the user's permission, allows or denies access to parts of the sitemap. There are various other ways this could be done without having to replace the Default Authentication components. Whatever works for you I suppose. Ralph Frangos, Nick (SAPOL) said: > > I still don't follow, once the XConfToolTask is executed how is the > AuthenticationManager you want to use reflected in the cocoon.roles file?. > Or should I not worry about this, simply modify my authentication.xroles > and > recreate the jars? Do I need to recreate the cocoon.war also?. > > For your curiosity: > I want to use my own AuthenticationManager to do role based > authentication. > I have already written an Authenticor, which gets the users info, along > with > there roles. But based on the roles, I want access-control to certain > areas > of the sitemap. > > > Nick Frangos > > -----Original Message----- > From: Ralph Goers [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 26 October 2004 12:43 AM > To: [EMAIL PROTECTED] > Subject: Re: Registering own Authentication Manager > > I'm pretty sure that authentication.xroles is patched in using > XConfToolTask (found in the tools directory) to cocoon.roles. > > I have to admit though, I'm a little curious as to why you'd want to > replace the Default Authentication Manager. I know others have replaced > the PipelineAuthenticator with their own Authenticator. Personally, I > found using the PipelineAuthenticator to work rather well. I simply wrote > a generator that performs all the authentication. It calls a session bean > to perform the login and then returns the required XML if login was > successful. > > > Frangos, Nick (SAPOL) said: >> I want to add my own Authentication Manager to be used instead of >> DefaultAUthenticationManager. >> >> I have found a response (below) on the mailing archive, but I require >> clarification. >> >> In regards to the response, I have found the authentication.xroles in my >> cocoon (2.1.5) src distro, but how is this included in my cocoon.jar? as >> indicated in the response. Also how is it "pathed" into cocoon.roles ? >> >> Is the initial response correct ?. >> >> >> List: xml-cocoon-users >> <http://marc.theaimsgroup.com/?l=xml-cocoon-users&r=1&w=2> >> Subject: Re: Registering own Authentication Manager >> <http://marc.theaimsgroup.com/?t=108187688200011&r=1&w=2> >> From: Joerg Heinicke <joerg.heinicke () gmx ! de> >> <http://marc.theaimsgroup.com/?a=102579193500001&r=1&w=2> >> Date: 2004-04-13 20:42:10 >> <http://marc.theaimsgroup.com/?l=xml-cocoon-users&r=1&w=2&b=200404> >> Message-ID: <407C50A2.4010105 () gmx ! de> >> > <http://marc.theaimsgroup.com/?i=%3C407C50A2.4010105%20%28%29%20gmx%20%21%20 >> de%3E> >> >> On 13.04.2004 19:21, [EMAIL PROTECTED] wrote: >> >>> Hi, >>> where can I register my own Authentication Manager (Authentication FW) >> instead >>> the default one? I searched for this particular configuration without >>> any >>> success in the files 'cocoon.xconf' and 'web.xml' >>> Best regards, >>> Mat >> >> Probably in cocoon.roles? >> >> > http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/src/blocks/authentication-fw/co >> nf/authent >> > <http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/src/blocks/authentication-fw/c >> onf/authent> \ >> ication.xroles?rev=1.4&view=markup >> >> is patched into >> >> > http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/src/java/org/apache/cocoon/coco >> on.roles?r >> > <http://cvs.apache.org/viewcvs.cgi/cocoon-2.1/src/java/org/apache/cocoon/coc >> oon.roles?r> \ >> ev=1.14&view=markup >> >> and ends in cocoon.jar. >> >> Joerg >> >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
