OASIS Key Management Interoperability Protocol (KMIP) TC

The response to Step 1 has hardcoded values for Data & IVCounterNonce.  I believe they should be parameterized as $DATA_0 & $IV_COUNTER_NONCE   Martin       Martin Shannon  Software Developer  QuintessenceLabs W: quintessencelabs.com      Unit 1 Lower Ground 15 Denison St Deakin ACT 2600 P: +61 2 6260 4922        World Economic Forum Technology Pioneer    Find out more at  quintessencelabs.com         

Thanks for pointing that out. The fixed values were left over from the test case it was copied from. With the RandomIV=true those items are indeed inherently variable. I've adjusted that in my set of test cases and will include that change in the next working draft upload version. Thanks, Tim. On Fri, Nov 22, 2019 at 11:09 AM Martin Shannon < ms@quintessencelabs.com > wrote: The response to Step 1 has hardcoded values for Data & IVCounterNonce. I believe they should be parameterized as $DATA_0 & $IV_COUNTER_NONCE Martin Martin Shannon Software Developer QuintessenceLabs W: quintessencelabs.com Unit 1 Lower Ground 15 Denison St Deakin ACT 2600 P: +61 2 6260 4922 World Economic Forum Technology Pioneer Find out more at quintessencelabs.com

Minor issue, there are two step 5     <ClientCorrelationValue type= TextString value= TC-DLOGIN-5-21 step=5 />   <BatchItem>     <Operation type= Enumeration value= Get />     <ClientCorrelationValue type= TextString value= TC-DLOGIN-5-21 step=5 />   <BatchItem>     <Operation type= Enumeration value= Destroy /> Best, Mark Joseph P6R, Inc 408-205-0361  

Another minor issue see below <ResponseMessage>   <ResponseHeader>     <ProtocolVersion>       <ProtocolVersionMajor type= Integer value= 2 />       <ProtocolVersionMinor type= Integer value= 1 />     </ProtocolVersion>     <TimeStamp type= DateTime value= $NOW />     <BatchCount type= Integer value= 1 />   </ResponseHeader>   <BatchItem>     <Operation type= Enumeration value= Archive />     <ResultStatus type= Enumeration value= OperationPending />     <AsynchronousCorrelationValue type= ByteString value= $ASYNCHRONOUS_CORRELATION_VALUE_0 />   </BatchItem> </ResponseMessage> <RequestMessage>   <RequestHeader>     <ProtocolVersion>       <ProtocolVersionMajor type= Integer value= 2 />       <ProtocolVersionMinor type= Integer value= 1 />     </ProtocolVersion>     <ClientCorrelationValue type= TextString value= TC-ASYNC-5-21 step=2 />     <BatchCount type= Integer value= 1 />   </RequestHeader>   <BatchItem>     <Operation type= Enumeration value= Process />     <RequestPayload>       <AsynchronousCorrelationValue type= ByteString value= $ASYNCHRONOUS_CORRELATION_VALUE / >     should have _0 at the end      </RequestPayload>   </BatchItem> </RequestMessage> Best, Mark Joseph P6R, Inc 408-205-0361

ASYNCHRONOUS_CORRELATION_VALUE_0 and ASYNCHRONOUS_CORRELATION_VALUE are entirely semantically equivalent. I will update that in the next release - but unless there are semantic changes I'll hold off on a new zip file. Tim. On Fri, Nov 29, 2019 at 6:36 AM Mark Joseph < mark@p6r.com > wrote: Another minor issue see below <ResponseMessage> <ResponseHeader> <ProtocolVersion> <ProtocolVersionMajor type="Integer" value="2"/> <ProtocolVersionMinor type="Integer" value="1"/> </ProtocolVersion> <TimeStamp type="DateTime" value="$NOW"/> <BatchCount type="Integer" value="1"/> </ResponseHeader> <BatchItem> <Operation type="Enumeration" value="Archive"/> <ResultStatus type="Enumeration" value="OperationPending"/> <AsynchronousCorrelationValue type="ByteString" value="$ASYNCHRONOUS_CORRELATION_VALUE_0"/> </BatchItem> </ResponseMessage> <RequestMessage> <RequestHeader> <ProtocolVersion> <ProtocolVersionMajor type="Integer" value="2"/> <ProtocolVersionMinor type="Integer" value="1"/> </ProtocolVersion> <ClientCorrelationValue type="TextString" value="TC-ASYNC-5-21 step=2"/> <BatchCount type="Integer" value="1"/> </RequestHeader> <BatchItem> <Operation type="Enumeration" value="Process"/> <RequestPayload> <AsynchronousCorrelationValue type="ByteString" value= "$ASYNCHRONOUS_CORRELATION_VALUE"/ > should have "_0" at the end </RequestPayload> </BatchItem> </RequestMessage> Best, Mark Joseph P6R, Inc 408-205-0361

Another minor issue Wrong test case and step number     <ClientCorrelationValue type= TextString value= TC-DLOGIN-13-21 step=6 />      should be   TC-DLOGIN-10-21 step=4   <BatchItem>     <Operation type= Enumeration value= Destroy /> wrong step number     <ClientCorrelationValue type= TextString value= TC-DLOGIN-10-21 step=7 />   <BatchItem>     <Operation type= Enumeration value= Interop /> Best, Mark Joseph P6R, Inc 408-205-0361

Another minor issue The test and step numbers are off for several requests starting on the second DelegatedLogin call     <ClientCorrelationValue type= TextString value= TC-DLOGIN-8-21 step=4 />     <Authentication>       <Credential>         <CredentialType type= Enumeration value= Ticket />         <CredentialValue>           <Ticket>             <TicketType type= Enumeration value= Login />             <TicketValue type= ByteString value= $TICKET_VALUE_0 />           </Ticket>         </CredentialValue>       </Credential>     </Authentication>     <BatchCount type= Integer value= 1 />   </RequestHeader>   <BatchItem>     <Operation type= Enumeration value= DelegatedLogin /> Best, Mark Joseph P6R, Inc 408-205-0361

More minor issues 1) In TC-DLOGIN-11-21     <ClientCorrelationValue type= TextString value= TC-DLOGIN-8-21 step=4 / >     <Authentication>       <Credential>         <CredentialType type= Enumeration value= Ticket />         <CredentialValue>           <Ticket>             <TicketType type= Enumeration value= Login />             <TicketValue type= ByteString value= $TICKET_VALUE_0 />           </Ticket>         </CredentialValue>       </Credential>     </Authentication>     <BatchCount type= Integer value= 1 />   </RequestHeader>   <BatchItem>     <Operation type= Enumeration value= DelegatedLogin />     <ClientCorrelationValue type= TextString value= TC-DLOGIN-13-21 step=8 />     <BatchOrderOption type= Boolean value= true />     <BatchCount type= Integer value= 2 />   </RequestHeader>   <BatchItem>     <Operation type= Enumeration value= Destroy /> 2) In TC-DLOGIN-12-21 Several ClientCorrelationValues have the wrong test number. Also see below:     <ClientCorrelationValue type= TextString value= TC-DLOGIN-13-21 step=7 />     <Authentication>       <Credential>         <CredentialType type= Enumeration value= Ticket />         <CredentialValue>           <Ticket>             <TicketType type= Enumeration value= Login />             <TicketValue type= ByteString valu e= $TICKET_VALUE />    <--- I believe both of these should be $TICKET_VALUE_1           </Ticket>     <ClientCorrelationValue type= TextString value= TC-DLOGIN-13-21 step=8 />     <Authentication>       <Credential>         <CredentialType type= Enumeration value= Ticket />         <CredentialValue>           <Ticket>             <TicketType type= Enumeration value= Login />             <TicketValue type= ByteString va lue= $TICKET_VALUE /> Best, Mark Joseph P6R, Inc 408-205-0361