Hi Enrique,

thanks for the answer, but i think these constraints only work IF YOU
KNOW THE USERNAME.

I have a template of a page for all users. Whenever a user is created,
this template is copied to the new user folder and THEN THE USERNAME HAS TO
BE DYNAMICALLY SET inside the security constraint.

I first thought maybe @username@ is dynamically replaced by jetspeed, but
that's not the case.

So how to constrain to the user dynamically ?

regards,
   Martin
--

. frankfurt am main, 31°c, die gefühlte temperatur
 liegt bei 33°c. zur zeit ein wenig bewölkt in 1128
 m. die sichtweite reicht weiter als 10 km. zur zeit
 leicht regen.

< martin maidhof
 [EMAIL PROTECTED]
 t +49 69 759003 14

 wemove digital solutions GmbH
 www.wemove.com



-----Ursprüngliche Nachricht----- Von: "Enrique Perez" <[EMAIL PROTECTED]>
An: "'Jetspeed Users List'" <[email protected]>
Gesendet: Donnerstag, 13. Juli 2006 16:17
Betreff: RE: J2: How to define security constraint <owner> ....


Hi Martin,

If you want a page that only the owner can edit, I think you should
include a security constraint in that page similar to this:

-----------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<page>
   ...
   <security-constraints>
         <users>@username@</users>
         <permissions>view,edit,help</permissions>
   </security-constraints>
</page>
-----------------------------------------------------

or


-----------------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<page>
   ...
   <security-constraints>
         <owner>@username@</owner>
   </security-constraints>
</page>
-----------------------------------------------------

Try this...

Regards,
Enrique

-----Mensaje original-----
De: Martin Maidhof [mailto:[EMAIL PROTECTED]
Enviado el: jueves, 13 de julio de 2006 14:56
Para: [email protected]
Asunto: J2: How to define security constraint <owner> ....

Hi,

i want to guarantee, that a page can only be edited by its owner
and no other user !
How to do that with declarative security constraints in PSML ?

For every new user the page is copied from a page in the
_user/template folder. What to specify in that "source page"
so that the copied page can only be edited by the user it
belongs to ?
The constraint "public-edit" allows editing for ALL users, so
i don't want to use that. Is it possible to define some
kind of "owner-edit" security constraint in the page.security file
and then refer to that one ?

The topic <owner> isn't described in the manuals:

http://portals.apache.org/jetspeed-2/guides/guide-security-declarative-
psml.html

Many thanks for every hint,
    Martin
--

. frankfurt am main, 30°c, die gefühlte temperatur
  liegt bei 31°c. zur zeit ein wenig bewölkt in 1219
  m. die sichtweite reicht weiter als 10 km.

< martin maidhof
  [EMAIL PROTECTED]
  t +49 69 759003 14

  wemove digital solutions GmbH
  www.wemove.com




---------------------------------------------------------------------
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]

Reply via email to