next up previous
Next: ovsec_kadm_get_principal Up: ovsec_kadm_randkey_principal Previous: List of parameter settings

Other tests

Number:
17
Reason:
Fails if database not initialized.

Number:
18
Reason:
Fails for non-existent principal.

Number:
19
Reason:
Fails for null keyblock pointer.

Number:
20
Priority:
High
Reason:
Pw_expiration is set to now + max_pw_life if policy exists and has non-zero max_pw_life.

Number:
21
Priority:
High
Reason:
Pw_expiration is set to 0 if policy exists and has zero max_pw_life.

Number:
22
Priority:
High
Reason:
Pw_expiration is set to 0 if no policy.

Number:
23
Priority:
High
Reason:
KRB5_KDC_REQUIRES_PWCHANGE bit is cleared when key is successfully changed.

Number:
24
Priority:
High
Reason:
Fails for user with no access bits, on other's password.

Number:
25
Priority:
High
Reason:
Fails for user with ``get'' but not ``modify'' access, on other's password.
V2 note:
Change-password instead of modify access.

Number:
26
Reason:
Fails for user with ``delete'' but not ``modify'' access, on other's password.
V2 note:
Change-password instead of modify access.

Number:
27
Reason:
Fails for user with ``add'' but not ``modify'' access, on other's password.
V2 note:
Change-password instead of modify access.

Number:
28
Reason:
Succeeds for user with ``get'' and ``modify'' access, on other's password.
Status:
Implemented
V2 note:
Change-password instead of modify access.

Number:
28.25
Priority:
High
Reason:
Fails for user with get and modify access on others password When conneceted with CHANGEPW_SERVICE
Status:
Implemented
V2 note:
Change-password instead of modify access.

Number:
28.5
Priority:
High
Reason:
Succeeds for user with ``modify'' but not ``get'' access, on other's password.
Status:
Implemented
V2 note:
Change-password instead of modify access.

Number:
29
Reason:
The new key that's assigned is truly random. XXX not sure how to test this.

Number:
30
Reason:
Succeeds for own key, no other access bits when connecting with CHANGEPW service
Status:
Implemented

Number:
31
Reason:
Succeeds for own key, no other access bits when connecting with ADMIM service
Status:
Implemented

Number:
32
Reason:
Cannot change ovsec_adm/history key
Status:
Implemented

Number:
33
Priority:
High
Reason:
Returns BAD_SERVER_HANDLE when a null server handle is passed in
Status:
Implemented

Number:
34
Priority:
Low
Reason:
Connects to correct server when mutliple handles exist
Conditions:
RPC

Number:
100
Version:
KADM5_API_VERSION_2
Reason:
Returns a key for each unique encryption type specified in the keysalts.


next up previous
Next: ovsec_kadm_get_principal Up: ovsec_kadm_randkey_principal Previous: List of parameter settings
Autobuild 2006-06-16