Next: ovsec_kadm_modify_principal
Up: KADM5 Admin API Unit
Previous: ovsec_kadm_create_principal
- Number:
- 2
- Reason:
- Fails on null principal.
- Status:
- Implemented
- Number:
- 5
- Priority:
- High
- Reason:
- Fails on nonexistent principal.
- Status:
- Implemented
- Number:
- 6
- Priority:
- High
- Reason:
- Fails when caller connected with CHANGEPW_SERVICE.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 7
- Priority:
- High
- Reason:
- Fails if caller has ``add'' access and not ``delete''.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 8
- Priority:
- High
- Reason:
- Fails if caller has ``modify'' access and not ``delete''.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 9
- Priority:
- High
- Reason:
- Fails if caller has ``get'' access and not ``delete''.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 10
- Priority:
- High
- Reason:
- Fails if caller has no access bits.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 11
- Priority:
- High
- Reason:
- Valid invocation.
- Status:
- Implemented
- Number:
- 12
- Priority:
- High
- Reason:
- Valid invocation (on principal with policy).
- 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_principal
Up: KADM5 Admin API Unit
Previous: ovsec_kadm_create_principal
Autobuild
2006-06-16