Locate and Get in single operation in KMIP(Key Management Interoperability Protocol)












0















Has anyone used a locate and get operation in single kmip request .I am getting a error because it's difficult to operate at same time.
As u can see the kmip request i am sending to my server.



<RequestMessage>
<RequestHeader>
<ProtocolVersion>
<ProtocolVersionMajor type="Integer" value="1"/>
<ProtocolVersionMinor type="Integer" value="2"/>
</ProtocolVersion>
<Authentication>
<Credential>
<CredentialType type="Enumeration" value="UsernameAndPassword"/>
<CredentialValue>
<Username type="TextString" value="vijans"/>
<Password type="TextString" value="asdf1234"/>
</CredentialValue>
</Credential>
</Authentication>
<BatchOrderOption type="Boolean" value="1"/>
<BatchCount type="Integer" value="2"/>
</RequestHeader>
<BatchItem>
<Operation type="Enumeration" value="Locate"/>
<UniqueBatchItemID type="ByteString" value="31303030303031"/>
<RequestPayload>
<Attribute>
<AttributeName type="TextString" value="Name"/>
<AttributeValue>
<NameValue type="TextString" value="new_ss_nv"/>
<NameType type="Enumeration" value="UninterpretedTextString"/>
</AttributeValue>
</Attribute>
</RequestPayload>
</BatchItem>
<BatchItem>
<Operation type="Enumeration" value="Get"/>
<UniqueBatchItemID type="ByteString" value="31303030303032"/>
<RequestPayload/>
</BatchItem>
</RequestMessage>


this is not valid because the get operation doesn't evolve use of unique identifier.can help somebody?










share|improve this question



























    0















    Has anyone used a locate and get operation in single kmip request .I am getting a error because it's difficult to operate at same time.
    As u can see the kmip request i am sending to my server.



    <RequestMessage>
    <RequestHeader>
    <ProtocolVersion>
    <ProtocolVersionMajor type="Integer" value="1"/>
    <ProtocolVersionMinor type="Integer" value="2"/>
    </ProtocolVersion>
    <Authentication>
    <Credential>
    <CredentialType type="Enumeration" value="UsernameAndPassword"/>
    <CredentialValue>
    <Username type="TextString" value="vijans"/>
    <Password type="TextString" value="asdf1234"/>
    </CredentialValue>
    </Credential>
    </Authentication>
    <BatchOrderOption type="Boolean" value="1"/>
    <BatchCount type="Integer" value="2"/>
    </RequestHeader>
    <BatchItem>
    <Operation type="Enumeration" value="Locate"/>
    <UniqueBatchItemID type="ByteString" value="31303030303031"/>
    <RequestPayload>
    <Attribute>
    <AttributeName type="TextString" value="Name"/>
    <AttributeValue>
    <NameValue type="TextString" value="new_ss_nv"/>
    <NameType type="Enumeration" value="UninterpretedTextString"/>
    </AttributeValue>
    </Attribute>
    </RequestPayload>
    </BatchItem>
    <BatchItem>
    <Operation type="Enumeration" value="Get"/>
    <UniqueBatchItemID type="ByteString" value="31303030303032"/>
    <RequestPayload/>
    </BatchItem>
    </RequestMessage>


    this is not valid because the get operation doesn't evolve use of unique identifier.can help somebody?










    share|improve this question

























      0












      0








      0








      Has anyone used a locate and get operation in single kmip request .I am getting a error because it's difficult to operate at same time.
      As u can see the kmip request i am sending to my server.



      <RequestMessage>
      <RequestHeader>
      <ProtocolVersion>
      <ProtocolVersionMajor type="Integer" value="1"/>
      <ProtocolVersionMinor type="Integer" value="2"/>
      </ProtocolVersion>
      <Authentication>
      <Credential>
      <CredentialType type="Enumeration" value="UsernameAndPassword"/>
      <CredentialValue>
      <Username type="TextString" value="vijans"/>
      <Password type="TextString" value="asdf1234"/>
      </CredentialValue>
      </Credential>
      </Authentication>
      <BatchOrderOption type="Boolean" value="1"/>
      <BatchCount type="Integer" value="2"/>
      </RequestHeader>
      <BatchItem>
      <Operation type="Enumeration" value="Locate"/>
      <UniqueBatchItemID type="ByteString" value="31303030303031"/>
      <RequestPayload>
      <Attribute>
      <AttributeName type="TextString" value="Name"/>
      <AttributeValue>
      <NameValue type="TextString" value="new_ss_nv"/>
      <NameType type="Enumeration" value="UninterpretedTextString"/>
      </AttributeValue>
      </Attribute>
      </RequestPayload>
      </BatchItem>
      <BatchItem>
      <Operation type="Enumeration" value="Get"/>
      <UniqueBatchItemID type="ByteString" value="31303030303032"/>
      <RequestPayload/>
      </BatchItem>
      </RequestMessage>


      this is not valid because the get operation doesn't evolve use of unique identifier.can help somebody?










      share|improve this question














      Has anyone used a locate and get operation in single kmip request .I am getting a error because it's difficult to operate at same time.
      As u can see the kmip request i am sending to my server.



      <RequestMessage>
      <RequestHeader>
      <ProtocolVersion>
      <ProtocolVersionMajor type="Integer" value="1"/>
      <ProtocolVersionMinor type="Integer" value="2"/>
      </ProtocolVersion>
      <Authentication>
      <Credential>
      <CredentialType type="Enumeration" value="UsernameAndPassword"/>
      <CredentialValue>
      <Username type="TextString" value="vijans"/>
      <Password type="TextString" value="asdf1234"/>
      </CredentialValue>
      </Credential>
      </Authentication>
      <BatchOrderOption type="Boolean" value="1"/>
      <BatchCount type="Integer" value="2"/>
      </RequestHeader>
      <BatchItem>
      <Operation type="Enumeration" value="Locate"/>
      <UniqueBatchItemID type="ByteString" value="31303030303031"/>
      <RequestPayload>
      <Attribute>
      <AttributeName type="TextString" value="Name"/>
      <AttributeValue>
      <NameValue type="TextString" value="new_ss_nv"/>
      <NameType type="Enumeration" value="UninterpretedTextString"/>
      </AttributeValue>
      </Attribute>
      </RequestPayload>
      </BatchItem>
      <BatchItem>
      <Operation type="Enumeration" value="Get"/>
      <UniqueBatchItemID type="ByteString" value="31303030303032"/>
      <RequestPayload/>
      </BatchItem>
      </RequestMessage>


      this is not valid because the get operation doesn't evolve use of unique identifier.can help somebody?







      java kmip






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 19 '18 at 6:20









      this_is_om_vmthis_is_om_vm

      474217




      474217
























          1 Answer
          1






          active

          oldest

          votes


















          1














          Your KMIP server must implement the ID placeholder mechanism. It's a temporary Unique Identifier variable to cache the identifier between batch items in a request
          (see the Client-to-Server Operations section in the specification).



          You can see for each operation how this ID placeholder must be used or saved. An extract from the Locate operation:




          The server returns a list of Unique Identifiers of the found objects,
          which then MAY be retrieved using the Get operation. [...]. If a
          single Unique Identifier is returned to the client, then the server
          SHALL copy the Unique Identifier returned by this operation into the
          ID Placeholder variable. If the Locate operation matches more than
          one object, and the Maximum Items value is omitted in the request, or
          is set to a value larger than one, then the server SHALL empty the ID
          Placeholder, causing any subsequent operations that are batched with
          the Locate, and which do not specify a Unique Identifier explicitly,
          to fail.




          In the Get operation, the Get Request Payload table specifies that the Unique Identifier is not required and describes that:




          If omitted, then the ID Placeholder value is used by the server as the
          Unique Identifier.




          Then for the Locate operation, if the Locate results with one single Unique Identifier, the server must cache the value in the ID placeholder (independently of the next operation), else it must empty the ID placeholder.



          Finally for the Get operation, if the Unique Identifier is not defined in the request, the server must make the operation with the ID placeholder. If the ID placeholder is empty, the operation must fail with a result like "Invalid Field" (i'm not sure about that result reason but that makes sense to me).






          share|improve this answer

























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53369284%2flocate-and-get-in-single-operation-in-kmipkey-management-interoperability-proto%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            1














            Your KMIP server must implement the ID placeholder mechanism. It's a temporary Unique Identifier variable to cache the identifier between batch items in a request
            (see the Client-to-Server Operations section in the specification).



            You can see for each operation how this ID placeholder must be used or saved. An extract from the Locate operation:




            The server returns a list of Unique Identifiers of the found objects,
            which then MAY be retrieved using the Get operation. [...]. If a
            single Unique Identifier is returned to the client, then the server
            SHALL copy the Unique Identifier returned by this operation into the
            ID Placeholder variable. If the Locate operation matches more than
            one object, and the Maximum Items value is omitted in the request, or
            is set to a value larger than one, then the server SHALL empty the ID
            Placeholder, causing any subsequent operations that are batched with
            the Locate, and which do not specify a Unique Identifier explicitly,
            to fail.




            In the Get operation, the Get Request Payload table specifies that the Unique Identifier is not required and describes that:




            If omitted, then the ID Placeholder value is used by the server as the
            Unique Identifier.




            Then for the Locate operation, if the Locate results with one single Unique Identifier, the server must cache the value in the ID placeholder (independently of the next operation), else it must empty the ID placeholder.



            Finally for the Get operation, if the Unique Identifier is not defined in the request, the server must make the operation with the ID placeholder. If the ID placeholder is empty, the operation must fail with a result like "Invalid Field" (i'm not sure about that result reason but that makes sense to me).






            share|improve this answer






























              1














              Your KMIP server must implement the ID placeholder mechanism. It's a temporary Unique Identifier variable to cache the identifier between batch items in a request
              (see the Client-to-Server Operations section in the specification).



              You can see for each operation how this ID placeholder must be used or saved. An extract from the Locate operation:




              The server returns a list of Unique Identifiers of the found objects,
              which then MAY be retrieved using the Get operation. [...]. If a
              single Unique Identifier is returned to the client, then the server
              SHALL copy the Unique Identifier returned by this operation into the
              ID Placeholder variable. If the Locate operation matches more than
              one object, and the Maximum Items value is omitted in the request, or
              is set to a value larger than one, then the server SHALL empty the ID
              Placeholder, causing any subsequent operations that are batched with
              the Locate, and which do not specify a Unique Identifier explicitly,
              to fail.




              In the Get operation, the Get Request Payload table specifies that the Unique Identifier is not required and describes that:




              If omitted, then the ID Placeholder value is used by the server as the
              Unique Identifier.




              Then for the Locate operation, if the Locate results with one single Unique Identifier, the server must cache the value in the ID placeholder (independently of the next operation), else it must empty the ID placeholder.



              Finally for the Get operation, if the Unique Identifier is not defined in the request, the server must make the operation with the ID placeholder. If the ID placeholder is empty, the operation must fail with a result like "Invalid Field" (i'm not sure about that result reason but that makes sense to me).






              share|improve this answer




























                1












                1








                1







                Your KMIP server must implement the ID placeholder mechanism. It's a temporary Unique Identifier variable to cache the identifier between batch items in a request
                (see the Client-to-Server Operations section in the specification).



                You can see for each operation how this ID placeholder must be used or saved. An extract from the Locate operation:




                The server returns a list of Unique Identifiers of the found objects,
                which then MAY be retrieved using the Get operation. [...]. If a
                single Unique Identifier is returned to the client, then the server
                SHALL copy the Unique Identifier returned by this operation into the
                ID Placeholder variable. If the Locate operation matches more than
                one object, and the Maximum Items value is omitted in the request, or
                is set to a value larger than one, then the server SHALL empty the ID
                Placeholder, causing any subsequent operations that are batched with
                the Locate, and which do not specify a Unique Identifier explicitly,
                to fail.




                In the Get operation, the Get Request Payload table specifies that the Unique Identifier is not required and describes that:




                If omitted, then the ID Placeholder value is used by the server as the
                Unique Identifier.




                Then for the Locate operation, if the Locate results with one single Unique Identifier, the server must cache the value in the ID placeholder (independently of the next operation), else it must empty the ID placeholder.



                Finally for the Get operation, if the Unique Identifier is not defined in the request, the server must make the operation with the ID placeholder. If the ID placeholder is empty, the operation must fail with a result like "Invalid Field" (i'm not sure about that result reason but that makes sense to me).






                share|improve this answer















                Your KMIP server must implement the ID placeholder mechanism. It's a temporary Unique Identifier variable to cache the identifier between batch items in a request
                (see the Client-to-Server Operations section in the specification).



                You can see for each operation how this ID placeholder must be used or saved. An extract from the Locate operation:




                The server returns a list of Unique Identifiers of the found objects,
                which then MAY be retrieved using the Get operation. [...]. If a
                single Unique Identifier is returned to the client, then the server
                SHALL copy the Unique Identifier returned by this operation into the
                ID Placeholder variable. If the Locate operation matches more than
                one object, and the Maximum Items value is omitted in the request, or
                is set to a value larger than one, then the server SHALL empty the ID
                Placeholder, causing any subsequent operations that are batched with
                the Locate, and which do not specify a Unique Identifier explicitly,
                to fail.




                In the Get operation, the Get Request Payload table specifies that the Unique Identifier is not required and describes that:




                If omitted, then the ID Placeholder value is used by the server as the
                Unique Identifier.




                Then for the Locate operation, if the Locate results with one single Unique Identifier, the server must cache the value in the ID placeholder (independently of the next operation), else it must empty the ID placeholder.



                Finally for the Get operation, if the Unique Identifier is not defined in the request, the server must make the operation with the ID placeholder. If the ID placeholder is empty, the operation must fail with a result like "Invalid Field" (i'm not sure about that result reason but that makes sense to me).







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Nov 24 '18 at 20:26

























                answered Nov 24 '18 at 17:42









                XamrixXamrix

                1757




                1757






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53369284%2flocate-and-get-in-single-operation-in-kmipkey-management-interoperability-proto%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Biblatex bibliography style without URLs when DOI exists (in Overleaf with Zotero bibliography)

                    ComboBox Display Member on multiple fields

                    Is it possible to collect Nectar points via Trainline?