IBM Web Content Manager - The IBM Learner Portal is currently ...

11: User access and security
In this section of the course you will learn how to use the access control features of IBM Web Content
Manager and WebSphere Portal to restrict access to a section of your website.
Time required
It should take approximately 3 hours to complete these lessons.
Learning objectives
When you have completed this part of the course you should be able to:
v Restrict access to a section of your site framework
v Restrict access to individual items
v Restrict access to a page
Lesson 11.0.1: Access controls
You can restrict access to selected users and groups to the views within an authoring portlet, the items
managed by the authoring portlet, and items, portlets, and pages displayed within a website.
There are multiple access control layers used by IBM Web Content Manager and WebSphere Portal. Both
use an "inheritance" model in which the access controls set on parent items can be automatically inherited
by their children. Different access control settings can then be applied to individual child items where
required.
WebSphere Portal access controls
You can control user access to pages and to specific portlets within WebSphere Portal. Access
settings are defined in a parent page and are automatically inherited by any child pages.
Although you cannot define access controls for individual portlets on a page, you can define
access controls for each type of portlet used by your system.
Web content libraries
Library-level access controls determine access to the library as a whole. If access is granted, it
provides an entry point to the library. A user needs at least contributor access to a library in order
to have access to it on the authoring portlet.
Item types per library
Item type access controls define the item type views and tasks a user can access within the
authoring portlet for a particular library. The permissions set for item types in a library do not
automatically give you access to individual items. They only give you access to specific tasks and
views within the authoring portlet.
Accompanying guide for SPVC - not for distribution
Item-level access controls
Item-level access controls define the actions that a user can perform on an individual item. For
example, a user with manager access to Components has access to the Purge and Unlock actions
but, if that user does not also have manager access to an individual component, then the Purge
and Unlock actions will not be enabled when that component is selected.
Lab 11.1: Adding a Confidential site area and related items
During this lab you will add to your site framework a new site area that will be used to store
confidential content items. Only users belonging to the Executives group will be able to access these
items.
177