Previous Contents Index Next |
Sun ONE Identity Server Administration Guide |
Chapter 2 Identity Management
This chapter describes the user management features of Sun ONE Identity Server. The Identity Management module interface provides a way to view, manage and configure all Identity Server objects and identities. This chapter contains the following sections:
The Identity Management Interface
The Identity Management Interface
There are two basic views of the Identity Server graphical user interface. Depending on the roles of the user logging in, they might gain access to the Identity Management View or the User Profile View.
Identity Management View
When a user with an administrative role authenticates to the Identity Server, their default view is the Identity Management view. In this view the administrator can perform administrative tasks. Depending on the role of the administrator, this can include, but is not limited to, creating objects (users, organizations, policies, and so forth), and configuring services.
Figure 2-1 Identity Management View with Organization Properties Displayed
User Profile View
When a user who has not been assigned an administrative role authenticates to the Identity Server, the default view is their own User Profile. In this view the user can modify the values of the attributes particular to their personal profile. This can include, but is not limited to, name, home address and password. The attributes displayed in the User Profile View can be extended. For more information on adding customized attributes for objects and identities, see the Sun One Identity Server Programmer's Guide.
Figure 2-2 User Profile View
Managing Identity Server Objects
The User Management interface contains all the components needed to view and manage the Identity Server objects (organizations, groups, users, services, roles and policies). This section explains the object types and details on how to configure them.
Properties Function
To view or modify an entry's properties, click the Properties arrow next to the object's name. Its attributes and corresponding values are displayed in the data pane. Different objects display different properties.
Organizations properties allow status modification between active and inactive, full DNS name, DNS alias name, and a list of unique attributes.
The Groups properties contains two views, the General view and the User view. The General view allows or disallows users to self-subscribe to the group. In the User view, if the group is static, the administrator can add and remove users. If the group is dynamic, the administrator can only modify the filter to control which users are members of the group. For more information on static and dynamic groups, see "Create a Managed Group".
User properties include, but are not limited to, basic user information such as first name, last name, home address, telephone number and password.
Service properties include any of the attributes listed in Part 3, "Attribute Reference Guide" depending on the service.
Role properties include role and permission descriptions and the services registered to the role.
Policy properties allow you to modify all aspects of the created policies, including rules, referrals, subjects, and so forth. See "Policy Management" for more information. See the Sun One Identity Server Programmer's Guide for information on how to extend an entry's properties.
Organizations
This object represents the top-level of a hierarchical structure used by an enterprise to manage its departments and resources. Upon installation, Identity Server dynamically creates a top-level organization (defined during installation) to manage the Identity Server enterprise configurations. Additional organizations can be created after installation to manage separate enterprises. All created organizations fall beneath the top-level organization.
Choose Organizations from the View menu in the Identity Management module.
Click New in the navigation pane.
Enter a value for the name of the Organization in the New Organization template.
Choose a status of active or inactive.
The default is active. This can be changed at any time during the life of the organization by selecting the Properties icon. Choosing inactive disables log in to the organization.
Enter the values, if desired, for the optional fields. The optional fields are:
Full DNS Name - Enter the full Domain Name System (DNS) name for the organization, if it has one.
DNS Alias Name - Allows you to add alias names for the DNS name for the organization.
Unique Attribute List - Allows you to add a list of unique attributes for users in the organization. For example, if you add a unique attribute specifying an email address, you would not be able to create two users with the same email address.
Enter the DNS alias name, and click Add to add it to the List of DNS Alias Names.
Enter a value for the unique attribute and click Add to add it to the Unique Attribute list.
Click Create.
Choose Organizations from the View menu in Identity Management.
All created organizations are displayed. To display specific organizations, enter a search string and click Filter.
Select the checkbox next to the name of the Organization to be deleted.
Note There is no warning message when performing a delete. All entries within the organization will be deleted.
Add an Organization to a Policy
Identity Server objects are added to a policy through the policy's subject definition. When a policy is created or modified, organizations, roles, groups, and users can be defined as the subject in the policy's Subject page. Once the subject is defined, the policy will be applied to the object. For more information, see "Modifying Policies".
Groups
A group represents a collection of users with a common function, feature or interest. Typically, this grouping has no privileges associated with it. Groups can exist at two levels, within an organization and within other managed groups as a sub group. Users can be added to Managed Groups either statically or dynamically (filtered).
Membership By Subscription. When you specify group membership by subscription, a static group is created based on the Managed Group Type you specify. If the Managed Group Type value is static, group members are added to a group entry using the groupOfNames or groupOfUniqueNames object class. If the Managed Group Type value is dynamic, a specific LDAP filter is used to search and return only user entries that contain the memberof attribute. For more information, see Managed Group Type.
Membership By Filter. A filtered group is a dynamic group that is created through the use of an LDAP filter. All entries are funneled through the filter and dynamically assigned to the group. The filter would look for any attribute in an entry and return those that contain the attribute. For example, if you were to create a group based on a building number, you can use the filter to return a list all users containing the building number attribute.
Navigate to the organization (or group) where the group will be created.
Choose Groups from the View menu.
Select the group type from within the data pane.
If a static subscription group is to be created, select Membership By Subscription.
Enter a name for the group in the Name field. Click Next.
Select the Users Can Subscribe to this Group attribute to allow users to subscribe to the group themselves.
Add users to the group by selecting Add from the Member List.
Enter the search criteria and click Filter. When the user list is returned, select the users you wish to add and click Submit. Adding users to the group is optional. They can be added after the group is created.
If a dynamic (LDAP filtered) group is to be created, select Membership By Filter and click Save.
Enter a name for the group in the Name field. Click Next.
Construct the LDAP search filter.
The fields used to construct the filter use either an OR or AND operator. All the fields listed in the UI are used. If a field is left blank it will match all possible entries for that particular attribute.
Navigate to the organization where the group exists.
Choose Groups from the View menu.
Select the checkbox next to the name of the group to be deleted.
Add a Group to a Policy
Identity Server objects are added to a policy through the policy's subject definition. When a policy is created or modified, organizations, roles, groups, and users can be defined as the subject in the policy's Subject page. Once the subject is defined, the policy will be applied to the object. For more information, see "Modifying Policies".
Users
Users represent the identity of a person. Users can be created and deleted, and added or removed from services, roles or groups through the Identity Management module.
Navigate to the organization where the user should be created.
Choose Users from the View menu.
Enter values for the required attributes and any optional fields.
Information on the user profile attributes can be found in "User Attributes".
Click Create.
Add a User to Services, Roles and Groups
Navigate to the Organization where the user should be modified.
Choose Users from the View menu.
In the Navigation pane, select the user you wish to modify and click the Properties arrow.
From the View menu in the Data pane, select Services, Roles or Groups.
Select the service, role, or group that to which you wish to add the user, and click Save.
Navigate to the Organization where the user exists.
Choose Users from the View menu.
Select the checkbox next to the name of the user to be deleted.
Add a User to a Policy
Identity Server objects are added to a policy through the policy's subject definition. When a policy is created or modified, organizations, roles, groups, and users can be defined as the subject in the policy's Subject page. Once the subject is defined, the policy will be applied to the object. For more information, see "Modifying Policies".
Services
Activating a service for an organization is a two step process. In the first step you need to register the service with the organization. After a service is registered, a template configured specifically for that organization must be created. For additional information, see Chapter 3 "Service Configuration." Only top-level administrators can register, unregister and assign services to their own profiles.
Navigate to the Organization where you will add services.
Choose Organizations from the View menu in the Identity Management module and select the organization from the navigation pane. The Location path displays the default top-level organization and chosen organization.
Choose Services from the View menu.
Select the checkbox next to the services to be added.
Create a Template for a Service
Navigate to the organization or role where the registered service exists.
Choose Organizations from the View menu in the Identity Management Management module and select the organization from the navigation pane.
Choose Services from the View menu.
Click the properties icon next to the name of the service to be activated.
The data pane displays the message No Template Available For This Service. Do you want to create it?
Click Create.
A template is created for this service for the parent organization or role. The data pane displays the default attributes and values for this service. Descriptions for the attributes for the default services are described in the "Attribute Reference Guide".
Accept or modify the default values and click Save.
Navigate to the organization where you will remove services.
Choose Organizations from the View menu in Identity Management module and select the organization from the navigation pane.
Choose Services from the View menu.
Roles
Roles are a Directory Server entry mechanism similar to the concept of a group. A group has members; a role has members. A role's members are LDAP entries that are said to possess the role. The criteria of the role itself is defined as an LDAP entry with attributes, identified by the Distinguished Name (DN) attribute of the entry. Directory Server has a number of different types of roles but Identity Server can manage only one of them: the managed role.
Note
The other Directory Server role types can still be used in a directory deployment; they just can not be managed by Identity Server.
Users can possess one or more roles. For example, a contractor role which has attributes from the Session Service and the URL Policy Agent Service might be created. Thus, when new contractors start, the administrator can assign them this role rather than setting separate attributes in the contractor entry. If the contractor were then to become a full-time employee, the administrator would just re-assign the user a different role.
Identity Server uses roles to apply access control instructions. When first installed, Identity Server configures access control instructions (ACIs) that define administrator permissions. These ACIs are then designated in roles (such as Organization Admin Role and Organization Help Desk Admin Role) which, when assigned to a user, define the user's access permissions.
Users can view their assigned roles only if the Display User's Roles attribute is enabled in the Administration Service. For more information, see "Display User's Roles".
Navigate to the navigation pane of the Organization where the role will be created.
Choose Roles from the View menu.
A set of default roles are created when an organization is configured, and are displayed in the navigation pane.
For descriptions of these roles, see "Dynamic Admin Roles ACIs" of the Attribute Reference section.
Click New in the navigation pane.
Enter a name for the role.
Enter a description of the role.
Choose the role type from the Type menu.
The role can be either an Administrative role or a Service role. The role type is used by the console to figure out where to start the user in the DIT. An administrative role notifies the console that the possessor of the role has administrative privileges; the service role notifies the console that the possessor is an end user.
Choose a default set of permissions to apply to the role from the Access Permission menu.
The permissions provide access to entries within the organization. They are discussed in the section "Default Role Permissions (ACIs)". (The default permissions shown are in no particular order.)
Generally, the No Permissions ACI is assigned to Service roles, while Administrative roles are assigned any of the default ACIs.
Click Create.
The created role is displayed in the Navigation pane and status information about the role is displayed in the Data pane. You can add or remove services to the Role by clicking the Edit link in the Services display. For more information, see "Role Properties View".
Navigate to the organization that contains the role for deletion.
Choose Organizations from the View menu in Identity Management and select the organization from the navigation pane. The Location path displays the default top-level organization and chosen organization.
Choose Roles from the View menu.
Navigate to the Organization that contains the role to modify.
Choose Roles from the View menu.
Select the role to modify and click on the Properties arrow.
Choose Users from the View menu in the Data pane.
Enter a user ID.
Search criteria can also be entered (including first name, last name or active/inactive) if specific user id information is not available.
Choose the users from the names returned by selecting the checkbox next to the user name.
Navigate to the Organization that contains the role to modify.
Choose Organizations from the View menu in the Identity Management module and select the organization from the navigation pane.
Choose Roles from the View menu.
Choose Users from the View menu.
Select the checkbox of the users for removal.
Add a Role to a Policy
Identity Server objects are added to a policy through the policy's subject definition. When a policy is created or modified, organizations, roles, groups, and users can be defined as the subject in the policy's Subject page. Once the subject is defined, the policy will be applied to the object. For more information, see "Modifying Policies".
Role Properties View
The Roles Properties view allows for customizing the services available to a role, and the access level for the service attributes, on a per-role basis. Using the Roles Properties view, an administrator can customize the Service and End User pages, and create service administrators who only have access to specific services. For example, an administrator can deny write-access to one or more attributes in the user services for a given role, and a user possessing this role will not be able to modify these attributes. A policy administrator role can be created by granting access to all policy services, but denying access to other services. An administrator possessing the policy administrator role will then be able to create and assign policies, but will be denied from performing user management tasks.
To display the Role Profile page, click on the Properties button associated with a given role in the Roles Properties page, as shown in Figure 2-3.
Figure 2-3 Role Profile View 
In the Role Properties page, click Edit in the Services listing. The Service Access page is displayed, as shown in Figure 2-4.
Choose a service that is to be granted to the role by clicking on the service name in the Display column. By default, a role has access to all services.
Figure 2-4    Service Access Page
In the Role Properties page, click Edit in the Service Attribute listing. The Attribute Access page is displayed, as shown in Figure 2-5.
Use the Jump menu to display the attributes for a particular service.
Assign an access level to an attribute by selecting the Read/Write or Read Only check boxes.
Note If neither the Read/Write or Read Only options are selected for a given attribute, read and write access to that attribute is denied.
Figure 2-5 Attribute Access Page
For more information on specific Service attributes, see Part 3 of this manual, the Attribute Reference Guide.
Policies
Policies define rules to help protect an organization's web resources. Although policy creation, modification and deletion is performed through the Identity Management module, the procedures are described in Policy Management.
Containers
The container entry is used when, due to object class and attribute differences, it is not possible to use an organization entry. It is important to remember that the Identity Server container entry and the Identity Server organization entry are not necessarily equivalent to the LDAP object classes organizationalUnit and organization. They are abstract Identity entries. Ideally, the organization entry will be used instead of the container entry.
Note The display of containers is optional. To view containers you must select Display Containers in Menu in the Identity Server Administration service.
Navigate to the Organization or Container where the new Container will be created.
Click New.
Enter the name of the Container to be created.
Navigate to the organization or container which contains the container to be deleted.
Choose Containers from the View menu.
Select the checkbox next to the name of the container to be deleted.
Note Deleting a container will delete all objects that exist in that Container. This includes all objects and sub containers.
People Containers
A People Container is the default LDAP organizational unit to which all users are assigned when they are created within an organization. People containers can be found at the organization level and at the people container level as a sub People Container. They can contain only other people containers and users. Additional people containers can be added into the organization, if desired.
Note The display of people containers is optional. To view People Containers you must select Show People Containers in the Identity Server Administration service.
Navigate to the organization or people container where the new people container will be created.
Click New.
Enter the name of the people container to be created.
Navigate to the organization or people container which contains the people container to be deleted.
Choose People Containers from the View menu.
Select the checkbox next to the name of the people container to be deleted.
Note Deleting a people container will delete all objects that exist in that people container. This includes all users and sub people containers.
Group Containers
A Group Container is used to manage groups. It can contain only groups and other group containers. The group container Groups is dynamically assigned as the parent entry for all managed groups. Additional group containers can be added, if desired.
Note The display of group containers is optional. To view group containers you must select Show Group Containers in the Identity Server Administration service.
Navigate to the organization or the group container which contains the group container to be created.
Choose group containers from the View menu.
Click New.
Enter a value in the Name field and click Create.
Navigate to the organization which contains the group container to be deleted.
Choose Group Containers from the View menu.
Select the checkbox next to the group container to be deleted.
Previous Contents Index Next
Copyright 2002 Sun Microsystems, Inc. All rights reserved.
Last Updated December 04, 2002