Next: ovsec_kadm_delete_principal
Up: KADM5 Admin API Unit
Previous: ovsec_kadm_destroy
- Number:
- 2
- Reason:
- Fails on null princ argument.
- Status:
- Implemented
- Number:
- 3
- Reason:
- Fails on null password argument.
- Status:
- Implemented
- Number:
- 4
- Reason:
- Fails on empty-string password argument.
- Status:
- Implemented
- Number:
- 5
- Reason:
- Fails when mask contains undefined bit.
- Status:
- Implemented
- Number:
- 6
- Reason:
- Fails when mask contains LAST_PWD_CHANGE bit.
- Status:
- Implemented
- Number:
- 7
- Reason:
- Fails when mask contains MOD_TIME bit.
- Status:
- Implemented
- Number:
- 8
- Reason:
- Fails when mask contains MOD_NAME bit.
- Status:
- Implemented
- Number:
- 9
- Reason:
- Fails when mask contains MKVNO bit.
- Status:
- Implemented
- Number:
- 10
- Reason:
- Fails when mask contains AUX_ATTRIBUTES bit.
- Status:
- Implemented
- Number:
- 11
- Reason:
- Fails when mask contains POLICY_CLR bit.
- Status:
- Implemented
- Number:
- 12
- Reason:
- Fails for caller with no access bits.
- Status:
- Implemented
- Number:
- 13
- Reason:
- Fails when caller has ``get'' access and not ``add''.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 14
- Reason:
- Fails when caller has ``modify'' access and not ``add''.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 15
- Reason:
- Fails when caller has ``delete'' access and not ``add''.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 16
- Reason:
- Fails when caller connected with CHANGEPW_SERVICE.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 17
- Reason:
- Fails on attempt to create existing principal.
- Status:
- Implemented
- Number:
- 18
- Reason:
- Fails when password is too short.
- Status:
- Implemented
- Number:
- 19
- Reason:
- Fails when password has too few classes.
- Status:
- Implemented
- Number:
- 20
- Reason:
- Fails when password is in dictionary.
- Status:
- Implemented
- Number:
- 21
- Reason:
- Nonexistent policy is rejected.
- Status:
- Implemented
- Number:
- 22
- Reason:
- Fails on invalid principal name.
- Status:
- Implemented
- Number:
- 23
- Reason:
- Valid invocation.
- Status:
- Implemented
- Number:
- 24
- Reason:
- Succeeds when caller has ``add'' access and another one.
- Status:
- Implemented
- Number:
- 28
- Reason:
- Succeeds when assigning policy.
- Status:
- Implemented
- Number:
- 29
- Priority:
- High
- Reason:
- Allows 0 (never) for princ_expire_time.
- Status:
- Implemented
- Number:
- 30
- Reason:
- Allows 0 (never) for pw_expiration when there's no policy.
- Status:
- Implemented
- Number:
- 31
- Reason:
- Allows 0 (never) for pw_expiration when there's a policy with
0 for pw_max_life.
- Status:
- Implemented
- Number:
- 32
- Reason:
- Accepts 0 (never) for pw_expiration when there's a policy with
non-zero pw_max_life, and sets pw_expiration to zero.
- Status:
- Implemented
- Number:
- 33
- Reason:
- Accepts and sets non-zero pw_expiration when no policy.
- Status:
- Implemented
- Number:
- 34
- Reason:
- Accepts and sets non-zero pw_expiration when there's a policy
with zero pw_max_life.
- Status:
- Implemented
- Number:
- 35
- Reason:
- Accepts and sets non-zero pw_expiration when there's a policy
with pw_max_life later than the specified pw_expiration.
- Status:
- Implemented
- Number:
- 36
- Reason:
- Accepts and sets non-zero pw_expiration greater than now_pw_max_life.
- Status:
- Implemented
- Number:
- 37
- Priority:
- High
- Reason:
- Sets pw_expiration to 0 (never) if there's no policy and no
specified pw_expiration.
- Status:
- Implemented
- Number:
- 38
- Priority:
- High
- Reason:
- Sets pw_expiration to 0 (never) if it isn't specified and the
policy has a 0 (never) pw_max_life.
- Status:
- Implemented
- Number:
- 39
- Priority:
- High
- Reason:
- Sets pw_expiration to now + pw_max_life if it isn't specified
and the policy has a non-zero pw_max_life.
- Status:
- Implemented
- Number:
- 40
- Priority:
- High
- Reason:
- Allows 0 (forever) for max_life.
- Status:
- Implemented
- Number:
- 41
- Priority:
- High
- Reason:
- Doesn't modify or free mod_name on success.
- Number:
- 42
- Priority:
- High
- Reason:
- Doesn't modify or free mod_name on failure.
- Number:
- 43
- Priority:
- High
- Reason:
- Returns BAD_SERVER_HANDLE when a null server handle is passed in
- Status:
- Implemented
- Number:
- 44
- Priority:
- Low
- Reason:
- Connects to correct server when mutliple handles exist
- Conditions:
- RPC
Next: ovsec_kadm_delete_principal
Up: KADM5 Admin API Unit
Previous: ovsec_kadm_destroy
Autobuild
2006-06-16