Configuration administrator
A configuration administrator determines which resources are available
within an instance, and the attributes of these resources. A configuration
administrator does this by:
- Defining configuration object types (CTs) and the attributes that COs based on these CTs can have
- Defining configuration object sets (COSs)
- Adding configuration objects (COs) to and removing COs from OUs
- Specifying or modifying the values of attributes
The scope of a configuration administrator can be either an entire
instance or a specific OU:
- A system configuration administrator (SA) can administer all the CTs, OUs, COs, and COSs of an instance. An SA has the role DniSA assigned to their user ID for SYSOU.
- An OU configuration administrator (OSA) can administer certain COs of a particular OU. Which COs an OSA can administer is determined by roles assigned to them by a UA or OUA (see Security administrator). An OSA has, assigned to their user ID for a particular business OU, a role containing at least one of the CTs shown in Table 1. Each of these CTs corresponds to a command. An OSA can issue only those commands for which they have a role that contains the corresponding CTs. For example, you can create an OSA who is authorized to specify only the second half of the RM LAU keys for a particular OU.
| CT name | Command | Notes |
|---|---|---|
| DniComOU | commit OU | Each of these CTs corresponds to a command that applies to an entire OU, not to COs within an OU. |
| DniAppOU | approve OU | |
| DniDepOU | deploy OU | |
| DniRejOU | reject OU | |
| DniRaOU | reject approve OU | |
| DniModOU | modify OU | |
| DniAddOU | add OU | Each of these CTs corresponds to a command that applies to one or more COs within an OU. Each of these CTs has one or more pseudo attributes of the form CT_name.attribute_name. These attributes are used to specify for which COs the corresponding command can be issued. |
| DniRemOU | remove OU | |
| DniListOU | list OU |