Next: ovsec_kadm_get_policy
Up: KADM5 Admin API Unit
Previous: ovsec_kadm_delete_policy
- Number:
- 1
- Reason:
- Fails for mask with undefined bit set.
- Conditions:
- RPC
- Number:
- 2
- Priority:
- High
- Reason:
- Fails if caller connected with CHANGEPW_SERVICE.
- Status:
- Implemented
- Number:
- 3
- Reason:
- Fails for mask with POLICY bit set.
- Number:
- 4
- Reason:
- Fails for mask with REF_COUNT bit set.
- Status:
- Implemented
- Number:
- 5
- Reason:
- Fails for invalid policy name.
- Number:
- 6
- Reason:
- Fails for non-existent policy name.
- Number:
- 7
- Reason:
- Fails for null policy name.
- Number:
- 8
- Priority:
- High
- Reason:
- Fails for empty-string policy name.
- Status:
- Implemented
- Number:
- 9
- Priority:
- High
- Reason:
- Accepts 0 for pw_min_life.
- Status:
- Implemented
- Number:
- 10
- Priority:
- High
- Reason:
- Accepts non-zero for pw_min_life.
- Status:
- Implemented
- Number:
- 11
- Priority:
- High
- Reason:
- Accepts 0 for pw_max_life.
- Status:
- Implemented
- Number:
- 12
- Priority:
- High
- Reason:
- Accepts non-zero for pw_max_life.
- Status:
- Implemented
- Number:
- 13
- Priority:
- High
- Reason:
- Accepts 0 for pw_min_length.
- Status:
- Implemented
- Number:
- 14
- Priority:
- High
- Reason:
- Accepts non-zero for pw_min_length.
- Status:
- Implemented
- Number:
- 15
- Priority:
- High
- Reason:
- Rejects 0 for pw_min_classes.
- Status:
- Implemented
- Number:
- 16
- Priority:
- High
- Reason:
- Accepts 1 for pw_min_classes.
- Status:
- Implemented
- Number:
- 17
- Priority:
- High
- Reason:
- Accepts 4 for pw_min_classes.
- Status:
- Implemented
- Number:
- 18
- Priority:
- High
- Reason:
- Rejects 5 for pw_min_classes.
- Status:
- Implemented
- Number:
- 19
- Priority:
- High
- Reason:
- Rejects 0 for pw_history_num.
- Status:
- Implemented
- Number:
- 20
- Priority:
- High
- Reason:
- Accepts 1 for pw_history_num.
- Status:
- Implemented
- Number:
- 21
- Priority:
- High
- Reason:
- Accepts 10 for pw_history_num.
- Status:
- Implemented
- Number:
- 22
- Priority:
- High
- Reason:
- Fails for user with no access bits.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 23
- Priority:
- High
- Reason:
- Fails for user with ``get'' but not ``modify''.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 24
- Reason:
- Fails for user with ``add'' but not ``modify.''
- Conditions:
- RPC
- Number:
- 25
- Reason:
- Fails for user with ``delete'' but not ``modify.''
- Conditions:
- RPC
- Number:
- 26
- Priority:
- High
- Reason:
- Succeeds for user with ``modify.''
- Status:
- Implemented
- Number:
- 27
- Reason:
- Succeeds for user with ``get'' and ``modify.''
- Number:
- 28
- Reason:
- Rejects null policy argument.
- Number:
- 29
- Reason:
- Rejects change which makes pw_min_life greater than
pw_max_life.
- Number:
- 30
- Priority:
- High
- Reason:
- Returns BAD_SERVER_HANDLE when a null server handle is passed in
- Status:
- Implemented
- Number:
- 31
- Priority:
- Low
- Reason:
- Connects to correct server when mutliple handles exist
- Conditions:
- RPC
Next: ovsec_kadm_get_policy
Up: KADM5 Admin API Unit
Previous: ovsec_kadm_delete_policy
Autobuild
2009-09-05