EXTERNALAUTHENTICATECALLBACK
#include "ltdic.h"
L_UINT32 pEXT_CALLBACK Your_Function(hNet, nChallenge, nResponse, nParameter, pUserData)
HDICOMNET hNet; |
/* handle to an existing DICOM Network */ |
L_UINT64 nChallenge; |
/* challenge code */ |
L_UINT64 nResponse; |
/* response code */ |
L_UINT64 nParameter; |
/* key */ |
L_VOID * pUserData; |
/* optional pointer to more parameters for the callback */ |
Determines whether the response code is a valid response for the challenge code. This function is available in Medical Suite toolkits.
Parameter |
Description |
hNet |
Handle to an existing DICOM Network. This is the handle returned from the L_DicomCreateNet function. |
nChallenge |
Value that represents the challenge code sent to the peer computer. This value is similar to a time stamp. This function will determine whether the response code in the nResponse parameter is a valid response for this challenge code. |
nResponse |
Value that represents the response code generated by the peer computer. This value is similar to a time stamp. This function will determine whether this response code is a valid response for the challenge code in the nChallenge parameter. |
nParameter |
Value that indicates the current mutual authentication key. |
pUserData |
Void pointer that you can use to pass one or more additional parameters that the callback function needs. To use this feature, assign a value to a variable or create a structure that contains as many fields as you need. Then, in this parameter, pass the address of the variable or structure, casting it to L_VOID *. The callback function, which receives the address in its own pUserData parameter, can cast it to a pointer of the appropriate data type to access your variable or structure. If the additional parameters are not needed, you can pass NULL in this parameter. |
Returns
DICOM_SUCCESS |
The response code and challenge code match. |
<> DICOM_SUCCESS |
The response code and challenge code do not match. |
Required DLLs and Libraries
LTDIC For a listing of the exact DLLs and Libraries needed, based on the toolkit version, refer to Files To Be Included With Your Application |
See Also
Functions: |
|
Topics: |
|
|
|
|
General Integrated Secure Communication Layer (ISCL) Information |
Example
For an example, refer to INTERNALAUTHENTICATECALLBACK.