Next: ovsec_kadm_chpass_principal
Up: KADM5 Admin API Unit
Previous: ovsec_kadm_modify_principal
- Number:
- 2
- Priority:
- High
- Reason:
- Fails if user connected with CHANGEPW_SERVICE.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 3
- Priority:
- High
- Reason:
- Fails for user with no access bits.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 4
- Reason:
- Fails for user with ``modify'' access and not ``add'' or
``delete''.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 5
- Reason:
- Fails for user with ``get'' access and not ``add'' or
``delete''.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 6
- Reason:
- Fails for user with ``modify'' and ``add'' but not ``delete''.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 7
- Reason:
- Fails for user with ``modify'' and ``delete'' but not ``add''.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 8
- Reason:
- Fails for user with ``get'' and ``add'' but not ``delete''.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 9
- Reason:
- Fails for user with ``get'' and ``delete'' but not ``add.''
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 10
- Reason:
- Fails for user with ``modify'', ``get'' and ``add'', but not
``delete''.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 11
- Reason:
- Fails for user with ``modify'', ``get'' and ``delete'', but
not ``add''.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 12
- Priority:
- High
- Reason:
- Fails for user with ``add'' but not ``delete''.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 13
- Priority:
- High
- Reason:
- Fails for user with ``delete'' but not ``add''.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 14
- Priority:
- High
- Reason:
- Succeeds for user with ``add'' and ``delete'', when that user
has non-name-based salt.
- Status:
- Implemented
- Number:
- 15
- Priority:
- High
- Reason:
- Fails if target principal name exists.
- Status:
- Implemented
- Number:
- 16
- Priority:
- High
- Reason:
- Returns BAD_SERVER_HANDLE when a null server handle is passed in
- Status:
- Implemented
- Number:
- 17
- Priority:
- Low
- Reason:
- Connects to correct server when mutliple handles exist
- Conditions:
- RPC
- Number:
- 18
- Priority:
- bug fix
- Reason:
- Returns NO_RENAME_SALT when asked to rename a principal whose
salt depends on the principal name.
- Status:
- Implemented
Next: ovsec_kadm_chpass_principal
Up: KADM5 Admin API Unit
Previous: ovsec_kadm_modify_principal
Autobuild
2006-06-16