OSF DCE Administration Guide--Core Components

Creating and Maintaining Principals, Groups, and Organizations
30.5.2.2 Changing Principal Information
Use the dcecp principal modify command to change any principal information except
the UNIX ID and user ID. The following example shows the principal modify command
used to change principal mahler’s object creation quota to 10.
dcecp> principal modify mahlar -quota 10
30.5.3 Deleting Principals and Aliases
If you delete a principal or an alias, the system automatically deletes any accounts for
that principal or alias. For example, if you delete the principal mahler, the mahler
composers classic account is also deleted. If you delete the principal alias gustav, you
also delete the gustav music_admin classic account. If you delete the group alias
music_admin, you also delete the gustav music_admin classic account. Be aware that
deleting a principal or a principal’s alias could orphan the objects that are owned by the
principal/UUID.
The following example shows the principal delete command used to delete the principal
named mahler:
dcecp> principal delete mahler
You can delete multiple principals or aliases with one principal delete command. To do
so, enclose the principal names in braces, separated by spaces. For example, to delete
the principals bach, britten, and mahler, you would enter the following:
dcecp> principal delete {bach britten mahler}
30.6 Extended Security Attributes for Principals
You can attach ERA instances to principals to manage several aspects of DCE login and
password security. ERAs are available to control
The level of authentication security required for principal login requests
Handling of invalid logins
Strength of principals’ passwords as well as generation of passwords for principals
Handling of login attempts by principals with expired passwords
These ERAs are introduced and explained in the following sections. See Chapter 32 for
information on how to use dcecp to attach these ERAs to principals.
124243 Tandem Computers Incorporated 307