Next: ovsec_kadm_create_policy
Up: KADM5 Admin API Unit
Previous: Other tests
- Number:
- 1
- Reason:
- Fails for null ent.
- Status:
- Implemented
- Number:
- 2
- Reason:
- Fails for non-existent principal.
- Status:
- Implemented
- Number:
- 3
- Priority:
- High
- Reason:
- Fails for user with no access bits, retrieving other principal.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 4
- Priority:
- High
- Reason:
- Fails for user with ``add'' but not ``get'', getting principal
other than his own, using ADMIN_SERVICE.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 5
- Reason:
- Fails for user with ``modify'' but not ``get'', getting
principal other than his own, using ADMIN_SERVICE.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 6
- Reason:
- Fails for user with ``delete'' but not ``get'', getting
principal other than his own, using ADMIN_SERVICE.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 7
- Reason:
- Fails for user with ``delete'' but not ``get'', getting
principal other than his own, using CHANGEPW_SERVICE.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 8
- Priority:
- High
- Reason:
- Fails for user with ``get'', getting principal other than his
own, using CHANGEPW_SERVICE.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 9
- Priority:
- High
- Reason:
- Succeeds for user without ``get'', retrieving self, using
ADMIN_SERVICE.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 10
- Reason:
- Succeeds for user without ``get'', retrieving self, using
CHANGEPW_SERVICE.
- Status:
- Implemented
- Number:
- 11
- Reason:
- Succeeds for user with ``get'', retrieving self, using
ADMIN_SERVICE.
- Status:
- Implemented
- Number:
- 12
- Reason:
- Succeeds for user with ``get'', retrieving self, using
CHANGEPW_SERVICE.
- Status:
- Implemented
- Number:
- 13
- Priority:
- High
- Reason:
- Succeeds for user with ``get'', retrieving other user, using
ADMIN_SERVICE.
- Status:
- Implemented
- Number:
- 14
- Reason:
- Succeeds for user with ``get'' and ``modify'', retrieving
other principal, using ADMIN_SERVICE.
- Status:
- Implemented
- Number:
- 15
- Priority:
- High
- Reason:
- Returns BAD_SERVER_HANDLE when a null server handle is passed in
- Status:
- Implemented
- Number:
- 16
- Priority:
- Low
- Reason:
- Connects to correct server when mutliple handles exist
- Conditions:
- RPC
- Number:
- 100
- Version:
- KADM5_API_VERSION_2
- Reason:
- If KADM5_PRINCIPAL_NORMAL_MASK is specified, the key_data and
tl_data fields are NULL/zero.
- Status:
- Implemented
- Number:
- 101
- Version:
- KADM5_API_VERSION_2
- Reason:
- If KADM5_KEY_DATA is specified, the key_data fields contain
data but the contents are all NULL.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 102
- Version:
- KADM5_API_VERSION_2
- Reason:
- If KADM5_KEY_DATA is specified, the key_data fields contain
data and the contents are all non-NULL.
- Conditions:
- local
- Status:
- Implemented
- Number:
- 103
- Version:
- KADM5_API_VERSION_2
- Reason:
- If KADM5_TL_DATA is specified, the tl_data field contains the
correct tl_data and no entries whose type is less than 256.
- Status:
- Implemented
Next: ovsec_kadm_create_policy
Up: KADM5 Admin API Unit
Previous: Other tests
Autobuild
2006-06-16