db_invoke

[Luke Howard]

Nikhil,

db_invoke is an extra layer of indirection, I added this initially so  
that interfaces between the KDC and backend could be easily added  
without changing the kdb dispatch table (principally to ease merges  
when this code was proprietary). Whether this approach is still valid  
is open to debate.

There is no implementation in any of the backends shipped with MIT;  
you'll need to implement this yourself.

-- Luke

On 02/02/2009, at 5:51 AM, Nikhil Mishra wrote:

> Hi All ,
>
>
> How is this function working ?
>
> check_allowed_to_delegate_to
>
> calls
>
> code = krb5_db_invoke(context,
>                          KRB5_KDB_METHOD_CHECK_ALLOWED_TO_DELEGATE,
>                          &req_data,
>                          &rep_data);
>
>
> and in my case dal_handle->lib_handle->vftabl.db_invoke is always  
> NULL .
>
> if (dal_handle->lib_handle->vftabl.db_invoke == NULL) {
>        status = KRB5_KDB_DBTYPE_NOSUP;
>        goto clean_n_exit;
>    }
>
>
> I dont see any implementation for db_invoke as well .
> Do we need to implement db_invoke and If so , why do I see it being  
> called
> at multiple places ?
>
> --Nikhil
> _______________________________________________
> krbdev mailing list             krbdev at mit.edu
> https://mailman.mit.edu/mailman/listinfo/krbdev
>

--
www.padl.com | www.fghr.net