-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 so a permission of _SELF to be used with _CHANGE and _VIEW since permissions are anded?
Hans Bakker sent the following on 3/15/2009 12:32 AM: > I agree that a new permission should be created to facilitate this > separated for change and view. Some companies allow the editing/view of > own data and some companies do not want that... > > I do not see the need for a new request.... > > Regards, > Hans > > On Sun, 2009-03-15 at 08:09 +0100, Bruno Busco wrote: >> So, may be we should change the partymgr/viewprofile so that with a >> permission like PARTYMGR_VIEWOWN (assigned by default to new users), >> only the own profile can be viewed/edited. >> Is this correct? >> >> 2009/3/14 BJ Freeman <[email protected]>: > I would think that they first created their login which then is creates > partyID record with the login and default Permission so they may see > that profile only. > > Bruno Busco sent the following on 3/14/2009 11:52 AM: >>>>> Hi, >>>>> I am trying the MyPortal new user registration. >>>>> When a new user is created than he cannot see and edit its own profile >>>>> because he has no privileges. >>>>> How can we fix this? >>>>> >>>>> Should we create a viewOWNprofile request that does not take a partyId >>>>> as parameter but only works on the actual userLoginId ? >>>>> >>>>> Thank you >>>>> -Bruno >>>>> >>>>> >>> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJvN8PrP3NbaWWqE4RAp05AJ42591n0ui8rkXQHlz75ImmadMaRgCg1ABB l08wvlBuBZ38j3/Hmk0F2QM= =1eZ1 -----END PGP SIGNATURE-----
