<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 11/27/2013 12:45 AM, Takahiro Shida
      wrote:<br>
    </div>
    <blockquote
cite="mid:CAP-ZCfrOECvdB-We-U8rwEv764AHy92aNACjHeDd1UWRdCsRLg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div style="font-family:arial,sans-serif;font-size:14px">
          <p>Hi all,</p>
          <p>I'm also interested in this issue.</p>
          <p>> Create a unified request identifier<br>
            > <a moz-do-not-send="true" title=""
href="https://blueprints.launchpad.net/nova/+spec/cross-service-request-id"
              target="_blank">https://blueprints.launchpad.net/nova/+spec/cross-service-request-id</a><br>
            <br>
            I checked this BP and the following review.<br>
            <a moz-do-not-send="true" title=""
              href="https://review.openstack.org/#/c/29480/"
              target="_blank">https://review.openstack.org/#/c/29480/</a><br>
            <br>
            There are many comments. Finally, this review looks rejected
            by "user specified correlation-id" is useless and insecure.<br>
            <br>
            >> 3. Enable keystone to generate "request
            identification" (we can call it 'request-token', for
            example).<br>
          </p>
        </div>
      </div>
    </blockquote>
    Lets not use the term Token.  Request Identifier is fine.<br>
    <br>
    <blockquote
cite="mid:CAP-ZCfrOECvdB-We-U8rwEv764AHy92aNACjHeDd1UWRdCsRLg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div style="font-family:arial,sans-serif;font-size:14px">
          <p>> -2<br>
            <br>
            So, this idea will be helpful to solve the
            "cross-service-request-id" problem.<br>
            Because the correlation-id specified by keystone.<br>
          </p>
        </div>
      </div>
    </blockquote>
    Can we make this "request envelope" so that we can put more
    information into the request than just an identifier?  Specifically,
    we are going to potentially want to put a set of trust Identifiers
    into a portion of the message to allow for secure delegation.<br>
    <br>
    <blockquote
cite="mid:CAP-ZCfrOECvdB-We-U8rwEv764AHy92aNACjHeDd1UWRdCsRLg@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div style="font-family:arial,sans-serif;font-size:14px">
          <p><br>
            How about nova guys and keystone guys ?</p>
          <div><br>
          </div>
        </div>
      </div>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
    </blockquote>
    <br>
  </body>
</html>