Questions concerning NAP (SoH Attribute size, GetSoHRequest gets called several times)

  hello

i have questions concerning nap architecture.

can please respond questions.

 

questions:

 

1)     can append several attributes same type (sohattributetypevendorspecific) to soh?

it looks because maxsohattributecount is defined have value 100 , inapsohprocessor::findnextattribute has index attribute.

i’m questioning sure.

because maxsohattributesize (=4000) might small data have transport.

 

2)    if click in napstat.exe on “try again” button sha getsohrequest gets three times called.

how can prevent behaviour or how can nap soh cache used right?

 

do have sohrequest , if exist return?

and if doesn’t exist construct request , call setsohrequest cache param set true?

thanks in advance!

1.       you can append several attributes of same type types – there cardinality restrictions – documented in napprotocol.idl.   can append vendorspecific  attribute multiple times.

a.       concerning maxsohattributesize = 4000 being small, note entire soh has size limit (must less maxnetworksohsize).  size restriction can overcome compression/hashing or multiple round trips between sha , shv

2.       getsohrequest called per qec connection (note single qec can register multiple connections).  must have 3 qec connections on system – have 3 qec’s enabled each have single connection registered

a.       yes should use cache soh – unless has been invalidated soh response shv or health state change has occurred.

Windows Server  >  Network Access Protection