Next: ovsec_kadm_modify_policy
Up: KADM5 Admin API Unit
Previous: ovsec_kadm_create_policy
- Number:
- 1
- Reason:
- Fails for null policy name.
- Number:
- 2
- Priority:
- High
- Reason:
- Fails for empty-string policy name.
- Status:
- Implemented
- Number:
- 3
- Reason:
- Fails for non-existent policy name.
- Number:
- 4
- Reason:
- Fails for bad policy name.
- Number:
- 5
- Priority:
- High
- Reason:
- Fails if caller connected with CHANGEPW_SERVICE.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 6
- Priority:
- High
- Reason:
- Fails for user with no access bits.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 7
- Priority:
- High
- Reason:
- Fails for user with ``add'' but not ``delete''.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 8
- Reason:
- Fails for user with ``modify'' but not ``delete''.
- Conditions:
- RPC
- Number:
- 9
- Reason:
- Fails for user with ``get'' but not ``delete.''
- Conditions:
- RPC
- Number:
- 10
- Priority:
- High
- Reason:
- Succeeds for user with only ``delete''.
- Status:
- Implemented
- Number:
- 11
- Reason:
- Succeeds for user with ``delete'' and ``add''.
- Number:
- 12
- Priority:
- High
- Reason:
- Fails for policy with non-zero reference count.
- Status:
- Implemented
- Number:
- 13
- Priority:
- High
- Reason:
- Returns BAD_SERVER_HANDLE when a null server handle is passed in
- Status:
- Implemented
- Number:
- 14
- Priority:
- Low
- Reason:
- Connects to correct server when mutliple handles exist
- Conditions:
- RPC
Next: ovsec_kadm_modify_policy
Up: KADM5 Admin API Unit
Previous: ovsec_kadm_create_policy
Autobuild
2009-09-05