RE: Cocoon 2.1 Authentication Bug? *Please* Help

[Sy...@swisscom.com]

Hello Carsten,

OK, you means that for the load-users function you have to write a pipeline like (by default all the users are in the file sunrise-user.xml):

<map:match pattern="sunrise-loaduser">
	<map:generate src="load-user-ldap.xml"/>	
	<map:transform type="ldap">   
	<map:serialize type="xml"/>	
</map:match>

This pipeline should return a file with the same structure as the file sunrise-loaduser.xml with all the users inside. Right??

Before that I need to enter in the "User management" page where there are all the links for the functions (add user, etc...). Do you mean that this page uses one (or many) of this functions (load-users, load-roles, etc...)??

Thanks
Regards
Sylvain



-----Message d'origine-----
De: Carsten Ziegeler [mailto:cziegeler@s-und-n.de]
Date: vendredi, 29. août 2003 14:17
À: dev@cocoon.apache.org
Objet: RE: Cocoon 2.1 Authentication Bug? *Please* Help




> -----Original Message-----
> From: Sylvain.Thevoz@swisscom.com [mailto:Sylvain.Thevoz@swisscom.com]
> Sent: Thursday, August 28, 2003 9:54 AM
> To: dev@cocoon.apache.org
> Subject: RE: Cocoon 2.1 Authentication Bug? *Please* Help
> 
> 
> Hello Carsten,
> 
> The authentication works very well and I can enter inside the portal.
> But inside the portal there are two "functions": User Management 
> and Portal Management. These "functions" use the portal-auth 
> action and the portal-conf and auth-conf generators.
> The problem is that I can't access to these "functions", the 
> error is "Cocoon couldn't find the resource requested".
> Before I changed the authentication pipeline and integrated a 
> LDAP transformer these "functions" worked very well.
> 
> How works the portal-auth action? Do the generators read a file 
> (sunrise-user.xml) or another session parameters?
> 
The tools use a configuration that is part of the handler configuration
in the sitemap:
                <configuration name="single-role-user-management">
                  <load-users uri="cocoon:raw:/sunrise-loaduser"/>
                  <load-roles uri="cocoon:raw:/sunrise-roles"/>
                  <new-user uri="cocoon:raw:/sunrise-newuser"/>
                  <new-role uri="cocoon:raw:/sunrise-newrole"/>
                  <change-user uri="cocoon:raw:/sunrise-changeuser"/>
                  <delete-role uri="cocoon:raw:/sunrise-delrole"/>
                  <delete-user uri="cocoon:raw:/sunrise-deluser"/>
                </configuration>

you have to adjust these pipelines as well to use ldap.

Carsten

RE: Cocoon 2.1 Authentication Bug? *Please* Help

[Carsten Ziegeler <cz...@s-und-n.de>]

> From: Sylvain.Thevoz@swisscom.com [mailto:Sylvain.Thevoz@swisscom.com]
> 
> Hello Carsten,
> 
> OK, you means that for the load-users function you have to write 
> a pipeline like (by default all the users are in the file 
> sunrise-user.xml):
> 
> <map:match pattern="sunrise-loaduser">
> 	<map:generate src="load-user-ldap.xml"/>	
> 	<map:transform type="ldap">   
> 	<map:serialize type="xml"/>	
> </map:match>
> 
> This pipeline should return a file with the same structure as the 
> file sunrise-loaduser.xml with all the users inside. Right??
> 
Yes.

> Before that I need to enter in the "User management" page where 
> there are all the links for the functions (add user, etc...). Do 
> you mean that this page uses one (or many) of this functions 
> (load-users, load-roles, etc...)??
> 
It uses first all load- functions. When you execute a function, like
add or delete, then these pipelines are called as well.

Carsten