setObjectRights

MARMCL01User2_(Delete)_2732404

Please refer to the attached image file...If I set an ojects permissions to 'Reserve' through the web interface then all the required parent permissions are also set (see right side of image). If I set the same object's permission to 'PERM_CHECKOUT' through a LAPI call then only the 'Reserve' permission is set. Is the LAPI functioning correctly? If so, how does one set the other permissions for the same user/group? It seems that 'RIGHT_UPDATE' replaces the currrent permissions instead of updating them.We have Livelink 9.1.0 installed on a WinNT 4 server.Any insight would be appreciated,Dave

eLink User

Message from Sean M Alderman via eLinkI just had to open a ticket on this a few weeks ago. The suggestedprocedure for modifying permissions via lapi was to callgetObjectRights() first and then use that permission set and | it withthe PERM_ that you want to set. LAPI uses a single integerfield to store permissions, so bitwise operations are in order here. For example if it was an 8 bit integer...these numbers are hypothetical!!!PERM_SEE = 0000 0001PERM_SEECONTENTS = 0000 0010PERM_CHECKOUT = 0010 0000... and so on...So if you did a GetObjectRight() and it returned 0000 0011 and youwanted to add PERM_CHECKOUT, it would go like this -0000 0011 | 0010 0000 = 0010 0011and use that as your perms param with RIGHT_UPDATE for SetObjectRight ifyou wanted to preserve the existing permission set.>From the tech that answered my ticket...> RIGHT_DELETE deletes the entire permission set for that user. It is > for removing permissions on an object for a user. RIGHT_ADD adds a> permission set for a user, hence giving the user permissions on the> object. RIGHT_UPDATE doesn't differentiate, it simply sets the perms> to whatever you specify.So the RIGHT_<...> constants refer to the user/group in question -ADD -> user/group does not exist in the aclUPDATE -> user/group does exist in the aclDELETE -> removes user/group in the acl (regardless of what perm set ispassed in).With Add and Update a complete permission set must be passed in, notjust a single PERM_<...> constant.My actual preference is a little more complicated... If I know what thepermissions should be, then I use the PERM_FULL & !( setObjectRights> Posted by MARMCL01User2 on 06/04/2002 10:27 AM> > Please refer to the attached image file...> > If I set an ojects permissions to 'Reserve' through the web interface then all the required parent permissions are also set (see right side of image). If I set the same object's permission to 'PERM_CHECKOUT' through a LAPI call then only the 'Reserve' permission is set. Is the LAPI functioning correctly? If so, how does one set the other permissions for the same user/group? It seems that 'RIGHT_UPDATE' replaces the currrent permissions instead of updating them.> > We have Livelink 9.1.0 installed on a WinNT 4 server.> > Any insight would be appreciated,> Dave> > [To reply to this thread, use your normal e-mail reply function.]> > ============================================================> > Attachment link: permission.gif> https://knowledge.opentext.com/knowledge/livelink.exe/2755272/permission.gif?func=doc.Fetch&nodeid=2755272&gt; > ============================================================> > Discussion: LAPI Discussion> https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=765428&objAction=view&gt; > Livelink Server:> https://knowledge.opentext.com/knowledge/livelink.exe&gt; > -- Sean M. AldermanITRACK Systems AnalystPACE/NCI - NASA Glenn Research Center(216) 433-2795Calling a windowed operating system "Windows" is like naming anautomobile "Wheels."