Provide server side kadm5_chpass_principal_3() with ks_tuple implementation.
We enable kadm5_chpass_principal_3() in the server side of the library. The client kadm5 library calls will still return the error KAMD5_KS_TUPLE_NO_SUPP. Signed-off-by: Nicolas Williams <nico@cryptonector.com>
This commit is contained in:

committed by
Nicolas Williams

parent
00bea41dcb
commit
af011f57fc
@@ -42,7 +42,8 @@ kadm5_chpass_principal(void *server_handle,
|
||||
krb5_principal princ,
|
||||
const char *password)
|
||||
{
|
||||
return __CALL(chpass_principal, (server_handle, princ, 0, password));
|
||||
return __CALL(chpass_principal, (server_handle, princ, 0,
|
||||
0, NULL, password));
|
||||
}
|
||||
|
||||
kadm5_ret_t
|
||||
@@ -53,14 +54,8 @@ kadm5_chpass_principal_3(void *server_handle,
|
||||
krb5_key_salt_tuple *ks_tuple,
|
||||
const char *password)
|
||||
{
|
||||
/*
|
||||
* We should get around to implementing this... This can be useful
|
||||
* for, e.g., x-realm principals. For now we need the _3() to get
|
||||
* certain applications written to the kadm5 API to build and run.
|
||||
*/
|
||||
if (n_ks_tuple > 0)
|
||||
return KADM5_KS_TUPLE_NOSUPP;
|
||||
return __CALL(chpass_principal, (server_handle, princ, keepold, password));
|
||||
return __CALL(chpass_principal, (server_handle, princ, keepold,
|
||||
n_ks_tuple, ks_tuple, password));
|
||||
}
|
||||
|
||||
kadm5_ret_t
|
||||
|
Reference in New Issue
Block a user