next up previous
Next: ovsec_kadm_destroy Up: KADM5 Admin API Unit Previous: Introduction

ovsec_kadm_init

Number:
1
Reason:
An empty string realm is rejected.
Status:
Implemented
V2 note:
The empty string is now passed as the realm field of the parameters structure.

Number:
2
Reason:
A realm containing invalid characters is rejected.
Status:
Implemented
V2 note:
The invalid character is now passed as the realm field of the parameters structure.

Number:
2.5
Reason:
A non-existent realm is rejected.
Status:
Implemented
V2 note:
The non-existent realm is now passed as the realm field of the parameters structure.

Number:
3
Reason:
A bad service name representing an existing principal (different from the client principal) is rejected.
Conditions:
RPC
Status:
Implemented

Number:
4
Reason:
A bad service name representing a non-existent principal is rejected.
Conditions:
RPC
Status:
Implemented

Number:
5
Reason:
A bad service name identical to the (existing) client name is rejected.
Conditions:
RPC
Status:
Implemented

Number:
6
Reason:
A null password causes password prompting.
Status:
Implemented

Number:
7
Reason:
An empty-string causes password prompting
Status:
Implemented

Number:
8
Reason:
An incorrect password which is the password of another user is rejected.
Conditions:
RPC
Status:
Implemented

Number:
9
Reason:
An incorrect password which isn't the password of any user is rejected.
Conditions:
RPC
Status:
Implemented

Number:
10
Reason:
A null client_name is rejected.
Status:
Implemented

Number:
12
Reason:
A client_name referring to a non-existent principal in the default realm is rejected.
Conditions:
RPC
Status:
Implemented

Number:
13
Reason:
A client_name referring to a non-existent principal with the local realm specified explicitly is rejected.
Conditions:
RPC
Status:
Implemented

Number:
14
Reason:
A client_name referring to a non-existent principal in a nonexistent realm is rejected.
Conditions:
RPC
Status:
Implemented

Number:
15
Reason:
A client_name referring to an existing principal in a nonexistent realm is rejected.
Conditions:
RPC
Status:
Implemented

Number:
16
Reason:
Valid invocation.
Status:
Implemented

Number:
17
Reason:
Valid invocation (explicit client realm).
Status:
Implemented

Number:
18
Reason:
Valid invocation (CHANGEPW_SERVICE).
Status:
Implemented

Number:
19
Reason:
Valid invocation (explicit service realm).
Status:
Implemented
V2 note:
The explicit realm is now passed as the realm field of the configuration parameters.

Number:
20
Reason:
Valid invocation (database access allowed after init).
Status:
Implemented

Number:
22
Reason:
A null password causes master-key prompting.
Conditions:
local
Status:
Implemented
V2 note:
Obsolete.

Number:
22.5
Reason:
A empty string password causes master-key prompting.
Conditions:
local
Status:
Implemented
V2 note:
Obsolete.

Number:
24
Reason:
Null service name is ignored in local invocation.
Conditions:
local
Status:
Implemented

Number:
25
Reason:
Non-null service name is ignored in local invocation.
Conditions:
local
Status:
Implemented

Number:
30
Reason:
Can init after failed init attempt.
Conditions:
local
Status:
Implemented

Number:
31
Priority:
High
Reason:
Return BAD_STRUCT_VERSION when the mask bits are set to invalid values
Status:
Implemented

Number:
32
Priority:
High
Reason:
Return BAD_STRUCT_VERSION when the mask bits are not set
Status:
Implemented

Number:
33
Priority:
High
Reason:
Return OLD_STRUCT_VERSION when attempting to use an old/unsupported structure version
Status:
Implemented

Number:
34
Priority:
High
Reason:
Return NEW_STRUCT_VERSION when attempting to use a newer version of of the structure then what is supported
Status:
Implemented

Number:
35
Priority:
High
Reason:
Return BAD_API_VERSION when the mask bits are set to invalid values
Status:
Implemented

Number:
36
Priority:
High
Reason:
Return BAD_API_VERSION when the mask bits are not set
Status:
Implemented

Number:
37
Priority:
High
Reason:
Return OLD_LIB_API_VERSION when using an old/unsuppored api version number
Conditions:
RPC
Status:
Implemented

Number:
38
Priority:
High
Reason:
Return OLD_SERVER_API_VERSION attempting to use an old/unsupported api version number
Conditions:
local
Status:
Implemented

Number:
39
Priority:
High
Reason:
Return NEW_LIB_API_VERSION when using a newer api version number then supported
Conditions:
RPC
Status:
Implemented

Number:
40
Priority:
High
Reason:
Return NEW_SERVER_API_VERSION when using a newer api version number then supported
Conditions:
local
Status:
Implemented

Number:
41
Priority:
High
Reason:
Return BAD_XXX_VERSION when the API and the structure version numbers are reversed
Status:
Implemented

Number:
42
Priority:
High
Reason:
Succeeds when using valid api and struct version numbers and masks
Status:
Implemented

Number:
43
Priority:
Low
Reason:
Returns two different server handle when called twice with same info

Number:
44
Priority:
Low
Reason:
Returns two different server handles when called twice with different info

Number:
45
Priority:
Bug fix, secure-install/3390
Reason:
Returns SECURE_PRINC_MISSING when ADMIN_SERVICE does not exist.
Status:
Implemented

Number:
46
Priority:
Bug fix, secure-install/3390
Reason:
Returns SECURE_PRINC_MISSING when CHANGEPW_SERVICE does not exist.
Status:
Implemented

Number:
100
Version:
KADM5_API_VERSION_2
Reason:
Obeys the profile field of the configuration parameters, if set.
Status:
Implemented

Number:
101
Version:
KADM5_API_VERSION_2
Reason:
Obeys the kadmind_port field of the configuration parameters, if set.
Conditions:
RPC
Status:
Implemented

Number:
102
Version:
KADM5_API_VERSION_2
Reason:
Obeys the admin_server field of the configuration parameters, if set with only an admin server name.
Conditions:
RPC
Status:
Implemented

Number:
102.5
Version:
KADM5_API_VERSION_2
Reason:
Obeys the admin_server field of the configuratin parameters, if set with a host name and port number.
Conditions:
RPC

Number:
103
Version:
KADM5_API_VERSION_2
Reason:
Obeys the dbname field of the configuration parameters, if set.
Conditions:
local
Status:
Implemented

Number:
104
Version:
KADM5_API_VERSION_2
Reason:
Obeys the admin_dbname field of the configuration parameters, if set.
Conditions:
local
Status:
Implemented

Number:
105
Version:
KADM5_API_VERSION_2
Reason:
Obeys the admin_lockfile field of the configuration parameters, if set.
Conditions:
local
Status:
Implemented

Number:
106
Version:
KADM5_API_VERSION_2
Reason:
Obeys the mkey_from_kbd field of the configuration parameters, if set.
Conditions:
local
Status:
Implemented

Number:
107
Version:
KADM5_API_VERSION_2
Reason:
Obeys the stash_file field of the configuration parameters, if set.
Conditions:
local
Status:
Implemented

Number:
108
Version:
KADM5_API_VERSION_2
Reason:
Obeys the mkey_name field of the configuration parameters, if set.
Conditions:
local
Status:
Implemented

Number:
109
Version:
KADM5_API_VERSION_2
Reason:
Obeys the max_life field of the configuration parameters, if set.
Conditions:
local
Status:
Implemented

Number:
110
Version:
KADM5_API_VERSION_2
Reason:
Obeys the max_rlife field of the configuration parameters, if set.
Conditions:
local
Status:
Implemented

Number:
111
Version:
KADM5_API_VERSION_2
Reason:
Obeys the expiration field of the configuration parameters, if set.
Status:
Implemented
Conditions:
local

Number:
112
Version:
KADM5_API_VERSION_2
Reason:
Obeys the flags field of the configuration parameters, if set.
Conditions:
local
Status:
Implemented

Number:
113
Version:
KADM5_API_VERSION_2
Reason:
Obeys the keysalts and num_keysalts field of the configuration parameters, if set.
Conditions:
local
Status:
Implemented

Number:
114
Version:
KADM5_API_VERSION_2
Reason:
Returns KADM5_BAD_SERVER_PARAMS if any client-only parameters are specified to server-side init.
Conditions:
local
Status:
Implemented

Number:
115
Version:
KADM5_API_VERSION_2
Reason:
Returns KADM5_BAD_CLIENT_PARAMS if any client-only parameters are specified to server-side init.
Conditions:
RPC
Status:
Implemented

Number:
116
Version:
KADM5_API_VERSION_2
Reason:
Two calls to init with clients having different privileges succeedes, and both clients maintain their correct privileges.
Priority:
Bug fix
Conditions:
RPC
Status:
Implemented

Number:
117
Version:
KADM5_API_VERSION_2
Reason:
The max_life field defaults to value specified in the API Functional Specification when kdc.conf is unreadable.
Priority:
Bug fix, krb5-admin/18
Conditions:
local
Status:
Implemented

Number:
150
Version:
KADM5_API_VERSION_2
Reason:
init_with_creds works when given an open ccache with a valid credential for ADMIN_SERVICE.
Conditions:
RPC
Status:
Implemented

Number:
151
Version:
KADM5_API_VERSION_2
Reason:
init_with_creds works when given an open ccache with a valid credential for CHANGEPW_SERVICE.
Conditions:
RPC
Status:
Implemented

Number:
152
Version:
KADM5_API_VERSION_2
Reason:
init_with_creds fails with KRB5_FCC_NOFILE (was KADM5_GSS_ERROR) when given an open ccache with no credentials.
Conditions:
RPC
Status:
Implemented

Number:
153
Version:
KADM5_API_VERSION_2
Reason:
init_with_creds fails with KRB5_CC_NOTFOUND (was KADM5_GSS_ERROR) when given an open ccache without credentials for ADMIN_SERVICE or CHANGEPW_SERVICE.
Conditions:
RPC
Status:
Implemented

Number:
154
Version:
KADM5_API_VERSION_2
Reason:
If the KRB5_KDC_PROFILE environment variable is set to a filename that does not exist, init fails with ENOENT.
Conditions:
RPC
Status:
Implemented


next up previous
Next: ovsec_kadm_destroy Up: KADM5 Admin API Unit Previous: Introduction
Autobuild 2006-06-16