22.12.2012 Views

Front cover - IBM Redbooks

Front cover - IBM Redbooks

Front cover - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

564 Lotus Security Handbook<br />

external control. See the WebSphere Portal Server product documentation and<br />

Help files for detailed instructions on using this portlet.<br />

Note: When giving a user permission to deploy portlets, ensure that the user<br />

is also in the WebSphere Application Server Administrative Role. It is possible<br />

to add the user to a group that is in the Administrative Role, or it is possible to<br />

add the user to this role under Security Center in the Administration Console<br />

for Application Server.<br />

Access rights<br />

There are five simple permissions that can be assigned to resources. One of<br />

these, DELEGATE, is the permission that permits an authorized person to<br />

change access controls. The others are: VIEW, EDIT, MANAGE, and CREATE.<br />

For more complete information about these permissions, and for examples of<br />

how each permission limits control to a resource, see the WebSphere<br />

Application Server documentation. Some particularly important access rights<br />

topics are <strong>cover</strong>ed here.<br />

DELEGATE permissions<br />

DELEGATE permission is required for an administrator or subadministrator. A<br />

user, or group of users, with DELEGATE permission for a resource, such as a<br />

portlet or place, can grant users permission for that resource. Users may only<br />

grant the same level or a lower of permission (VIEW, EDIT, MANAGE, CREATE)<br />

for a resource that they themselves have for that resource. DELEGATE<br />

permission does not imply other access rights. Users with DELEGATE cannot<br />

assign a permission higher than they hold. For example, if Sandy has EDIT and<br />

DELEGATE on the Financial page and DELEGATE on the user group of which<br />

Fred is a member, then Sandy can assign VIEW or EDIT permissions for the<br />

Financial page to Fred or any other user in the same group as Fred. However,<br />

Sandy cannot assign MANAGE for that page because Sandy herself does not<br />

have MANAGE permission for that page.<br />

Access levels<br />

Newly created resources have a very specific initial access control state. Only<br />

the user who created the resource has any permissions for that resource.<br />

Likewise, the creator always has MANAGE and DELEGATE permissions for the<br />

new resource. If the creator also has access to the Access Control List portlet,<br />

that user can then grant other users access to that portlet within the restrictions<br />

discussed in the previous section. Portal administrators can also see the new<br />

resource and, if necessary, can grant themselves permissions which then allow<br />

them to share that resource with other users. Users must have the appropriate<br />

active or current minimum permission to access a resource. Active permissions<br />

can be inherited from the groups to which a user or user group belongs. Current

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!