Next: ovsec_kadm_rename_principal
Up: KADM5 Admin API Unit
Previous: ovsec_kadm_delete_principal
- Number:
- 2
- Priority:
- High
- Reason:
- Fails if user connected with CHANGEPW_SERVICE.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 3
- Reason:
- Fails on mask with undefined bit set.
- Status:
- Implemented
- Number:
- 4
- Reason:
- Fails on mask with PRINCIPAL set.
- Status:
- Implemented
- Number:
- 5
- Priority:
- High
- Reason:
- Fails on mask with LAST_PWD_CHANGE set.
- Status:
- Implemented
- Number:
- 6
- Reason:
- Fails on mask with MOD_TIME set.
- Status:
- Implemented
- Number:
- 7
- Reason:
- Fails on mask with MOD_NAME set.
- Status:
- Implemented
- Number:
- 8
- Reason:
- Fails on mask with MKVNO set.
- Status:
- Implemented
- Number:
- 9
- Priority:
- High
- Reason:
- Fails on mask with AUX_ATTRIBUTES set.
- Status:
- Implemented
- Number:
- 10
- Reason:
- Fails on nonexistent principal.
- Status:
- Implemented
- Number:
- 11
- Priority:
- High
- Reason:
- Fails for user with no access bits.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 12
- Priority:
- High
- Reason:
- Fails for user with ``get'' access.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 13
- Priority:
- High
- Reason:
- Fails for user with ``add'' access.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 14
- Priority:
- High
- Reason:
- Fails for user with ``delete'' access.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 15
- Priority:
- High
- Reason:
- Succeeds for user with ``modify'' access.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 16
- Reason:
- Succeeds for user with ``modify'' and another access.
- Conditions:
- RPC
- Status:
- Implemented
- Number:
- 17
- Priority:
- High
- Reason:
- Fails when nonexistent policy is specified.
- Status:
- Implemented
- Number:
- 18
- Priority:
- High
- Reason:
- Succeeds when existent policy is specified.
- Status:
- Implemented
- Number:
- 19
- Reason:
- Updates policy count when setting policy from none.
- Status:
- Implemented
- Number:
- 20
- Reason:
- Updates policy count when clearing policy from set.
- Status:
- Implemented
- Number:
- 21
- Reason:
- Updates policy count when setting policy from other policy.
- Status:
- Implemented
- Number:
- 21.5
- Reason:
- Policy reference count remains unchanged when policy is
changed to itself.
- Status:
- Implemented.
- Number:
- 22
- Reason:
- Allows 0 (never) for pw_expiration when there's no policy.
- Status:
- Implemented
- Number:
- 23
- Reason:
- Allows 0 (never) for pw_expiration when there's a policy with
0 for pw_max_life.
- Status:
- Implemented
- Number:
- 24
- Reason:
- Accepts 0 (never) for pw_expiration when there's a policy with
non-zero pw_max_life, but actually sets pw_expiration to
last_pwd_change + pw_max_life.
- Status:
- Implemented
- Number:
- 25
- Reason:
- Accepts and sets non-zero pw_expiration when no policy.
- Status:
- Implemented
- Number:
- 26
- Reason:
- Accepts and sets non-zero pw_expiration when there's a policy
with zero pw_max_life.
- Status:
- Implemented
- Number:
- 27
- 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:
- 28
- Reason:
- Accepts non-zero pw_expiration and limits it to last_pwd_change +
pw_max_life when it's later than last_pwd_change + non-zero
pw_max_life in policy.
- Status:
- Implemented
- Number:
- 29
- Priority:
- High
- Reason:
- Sets pw_expiration to 0 (never) when a policy is cleared and
no pw_expiration is specified.
- Status:
- Implemented
- Number:
- 30
- Priority:
- High
- Reason:
- Sets pw_expiration to 0 (never) if it isn't specified and the
new policy has a 0 (never) pw_max_life.
- Status:
- Implemented
- Number:
- 31
- Priority:
- High
- Reason:
- Sets pw_expiration to now + pw_max_life if it isn't specified
and the new policy has a non-zero pw_max_life.
- Status:
- Implemented
- Number:
- 32
- Priority:
- High
- Reason:
- Accepts princ_expire_time change.
- Status:
- Implemented
- Number:
- 33
- Priority:
- High
- Reason:
- Accepts attributes change.
- Status:
- Implemented
- Number:
- 33.25
- Priority:
- High
- Reason:
- Accepts attributes change (KRB5_KDB_REQUIRES_PW_CHANGE).
- Status:
- Implemented
- Number:
- 33.5
- Priority:
- High
- Reason:
- Accepts attributes change (KRB5_DISALLOW_TGT_BASE).
- Status:
- Implemented
- Number:
- 33.75
- Priority:
- High
- Reason:
- Accepts attributes change (KRB5_PW_CHANGE_SERVICE).
- Status:
- Implemented
- Number:
- 34
- Priority:
- High
- Reason:
- Accepts max_life change.
- Status:
- Implemented
- Number:
- 35
- Priority:
- High
- Reason:
- Accepts kvno change.
- Status:
- Implemented
- Number:
- 36
- Reason:
- Behaves correctly when policy is set to the same as it was
before.
- Status:
- Implemented
- Number:
- 37
- Reason:
- Behaves properly when POLICY_CLR is specified and there was no
policy before.
- Status:
- Implemented
- Number:
- 38
- Priority:
- High
- Reason:
- Accepts 0 (never) for princ_expire_time.
- Status:
- Implemented
- Number:
- 39
- Priority:
- High
- Reason:
- Accepts 0 for max_life.
- Status:
- Implemented
- Number:
- 40
- Reason:
- Rejects null principal argument.
- 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
- Number:
- 100
- Version:
- KADM5_API_VERSION_2
- Priority:
- bug-fix
- Reason:
- Accepts max_rlife change.
- Status:
- Implemented
- Number:
- 101
- Version:
- KADM5_API_VERSION_2
- Reason:
- Rejects last_success change.
- Status:
- Implemented
- Number:
- 102
- Version:
- KADM5_API_VERSION_2
- Reason:
- Rejects last_failed change.
- Status:
- Implemented
- Number:
- 103
- Version:
- KADM5_API_VERSION_2
- Reason:
- Rejects fail_auth_count change.
- Status:
- Implemented
- Number:
- 103.5
- Version:
- KADM5_API_VERSION_2
- Reason:
- Rejects key_data change.
- Status:
- Implemented
- Number:
- 104
- Version:
- KADM5_API_VERSION_2
- Reason:
- Accepts tl_data change when all types are greater than 256.
- Status:
- Implemented
- Number:
- 105
- Version:
- KADM5_API_VERSION_2
- Reason:
- Returns KADM5_BAD_TL_TYPE when given tl_data with a type less
than 256.
- Status:
- Implemented
Next: ovsec_kadm_rename_principal
Up: KADM5 Admin API Unit
Previous: ovsec_kadm_delete_principal
Autobuild
2006-06-16