...
| Excerpt |
|---|
...
Officers with appropriate roles are able to create, configure, and remove the various entities that make up a CA, such as:
- Domains
- Certificates
- Keys
- Policies
- Officers
See Certificate Authority (CA) administration tasks for a list of the tasks that you can do using the AWB.
...
| title | The AWB user interface |
|---|
The AWB user interface is an Explorer style browser where an entity can be selected and its information viewed.
The main window presents:
- a hierarchical view of the entities in the left-hand pane (explorer bar)
- information about a selected entity or a system summary in the right-hand pane (information pane).
These are the CA administration entities:
...
Domains are hierarchical. The top domain is called Root. In general, officers can only manipulate objects that belong to their own domain or subdomain. Super objects can be used and viewed, but not modified, if they are marked as visible in subdomain. If an object does not have a domain association, it belongs to the Root and it can be referenced from all domains.Can be used to group, for example, geographically separated regions.
...
The CA Hierarchy group provides access to all the CAs and secondary CAs of the system, displayed as hierarchical CA chains. The root of each CA chain is either a self-signed CA or a CA with an absent signer.
...
The Key Registry group provides access to the CA keys that have been created in the system, organized into three subgroups:
- Not In Use - those not yet used in a CA.
- In Use - those currently being used.
- Retired - those no longer in use.
...
The Policy group provides access to the procedures, rules, and formats used for issuing tokens and end-user certificates with the CAs. There are several organizational subgroups:
- Token, Certificate, Attribute certificate, Key, Publication, CIL and CRL procedures
- Distribution rules
- Certificate, Attribute certificate, Key procedure, Publication, CIL and CRL formats
...
The Officer Profiles group provides access to the officer roles created for the system. Officers are assigned roles, which allow them to perform various tasks. Roles are defined in officer profiles and one officer profile has to be selected for each officer created.
...
Audit provides access to the audit logs. All significant actions performed by or within the system are logged. Unlike the other groups, all information presented here is strictly read-only. There are no organizational subgroups, only two static entities: CIS log and Request log.
...
Selected entities from the other groups may be organized in folders in the same way as files are organized in a hierarchical file system. This can be useful for collecting all information relevant to a particular CA in a single folder.
...
is used by administration officers for setting up CA-unique configurations. |
Tasks done in AWB
Instructions for all tasks that are done in the AWB can be found here:
More information
| Child pages (Children Display) |
|---|
- Smart ID Certificate Manager
- Authority administration tasks in Certificate Manager
- Officers and roles in Certificate Manager
- Administration tasks in Certificate Manager