<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    El 23/05/12 17:42, Dolph Mathews escribió:
    <blockquote
cite="mid:CACgyLQYShNhC2CR7nEG3SugRdx_X2v7=NXVkTpebFM7SHNT1EQ@mail.gmail.com"
      type="cite">I haven't tested it myself, but I imagine you *could*
      deploy legacy_token_auth (which rewrites from keystone
      stable/diablo or essex-3 with stable/essex or folsom; however,
      there are a couple of issues that need to be resolved first.
      <div>
        <br>
      </div>
      <div>    <a moz-do-not-send="true"
href="https://github.com/openstack/keystone/blob/stable/diablo/keystone/frontends/legacy_token_auth.py"
          target="_blank">https://github.com/openstack/keystone/blob/stable/diablo/keystone/frontends/legacy_token_auth.py</a></div>
      <div><br>
      </div>
      <div>First issue: legacy_token_auth imports from legacy
        keystone.utils; however, they are trivial functions and could be
        moved into legacy_token_auth with an additional import for
        webob.Response.</div>
      <div>
        <br>
      </div>
      <div>Second issue: legacy_token_auth is dependent on the
        KEYSTONE_API_VERSION WSGI env var set by the urlrewritefilter
        middleware deployed in front of it. A simplified derivative of
        this middleware is included in folsom-m1
        (keystone.middleware.core.NormalizingFilter) which doesn't look
        at the Accept headers or API path prefix at all.</div>
      <div><br>
      </div>
      <div>    Diablo's NormalizingFilter: <a moz-do-not-send="true"
href="https://github.com/openstack/keystone/blob/stable/diablo/keystone/middleware/url.py"
          target="_blank">https://github.com/openstack/keystone/blob/stable/diablo/keystone/middleware/url.py</a></div>
      <div><br>
      </div>
      <div>    Folsom's NormalizingFilter: <a moz-do-not-send="true"
href="https://github.com/openstack/keystone/blob/master/keystone/middleware/core.py"
          target="_blank">https://github.com/openstack/keystone/blob/master/keystone/middleware/core.py</a></div>
      <div><br>
      </div>
      <div>Of course, there's also a bit of required config:</div>
      <div><br>
      </div>
      <div>   <a moz-do-not-send="true"
href="https://github.com/openstack/keystone/blob/stable/diablo/etc/keystone.conf"
          target="_blank">https://github.com/openstack/keystone/blob/stable/diablo/etc/keystone.conf</a></div>
      <div><br>
      </div>
      <div>I expect the actual request-rewriting of legacy_auth_token
        should work just fine against keystone trunk.</div>
      <div><br>
      </div>
      <div>-Dolph</div>
      <div><br>
      </div>
      <br>
      <div class="gmail_quote">On Wed, May 23, 2012 at 10:28 AM, Nguyen,
        Liem Manh <span dir="ltr"><<a moz-do-not-send="true"
            href="mailto:liem_m_nguyen@hp.com" target="_blank">liem_m_nguyen@hp.com</a>></span>
        wrote:<br>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">
          <div link="blue" vlink="purple" lang="EN-US">
            <div>
              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">In
                  essex-3, there used to be a “legacy_token_auth”
                  component that does just this.</span></p>
              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Liem</span></p>
              <p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"> </span></p>
              <div style="border:none;border-top:solid #b5c4df
                1.0pt;padding:3.0pt 0in 0in 0in">
                <p class="MsoNormal"><b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span
style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">
                    openstack-bounces+liem_m_nguyen=<a
                      moz-do-not-send="true"
                      href="mailto:hp.com@lists.launchpad.net"
                      target="_blank">hp.com@lists.launchpad.net</a>
                    [mailto:<a moz-do-not-send="true"
                      href="mailto:openstack-bounces%2Bliem_m_nguyen"
                      target="_blank">openstack-bounces+liem_m_nguyen</a>=<a
                      moz-do-not-send="true"
                      href="mailto:hp.com@lists.launchpad.net"
                      target="_blank">hp.com@lists.launchpad.net</a>]
                    <b>On Behalf Of </b>Chmouel Boudjnah<br>
                    <b>Sent:</b> Wednesday, May 23, 2012 6:54 AM<br>
                    <b>To:</b> Christian Broussard<br>
                    <b>Cc:</b> <a moz-do-not-send="true"
                      href="mailto:openstack@lists.launchpad.net"
                      target="_blank">openstack@lists.launchpad.net</a><br>
                    <b>Subject:</b> Re: [Openstack]
                    [OpenStack][Keystone]Does legacy_auth v1.0 exist in
                    Keystone Essex ?</span></p>
              </div>
              <div>
                <div class="h5">
                  <p class="MsoNormal"> </p>
                  <p class="MsoNormal">On Wed, May 23, 2012 at 3:53 PM,
                    Christian Broussard <<a moz-do-not-send="true"
                      href="mailto:christian.broussard@gmail.com"
                      target="_blank">christian.broussard@gmail.com</a>>
                    wrote:</p>
                  <div>
                    <blockquote style="border:none;border-left:solid
                      #cccccc 1.0pt;padding:0in 0in 0in
                      6.0pt;margin-left:4.8pt;margin-right:0in">
                      <p class="MsoNormal">I'm interested in this topic
                        as well.  Chmouel, are you indicated that
                        without a 3rd party middleware implementation,
                        there is no way to handle v1.0 auth with
                        keystone/swift?</p>
                    </blockquote>
                    <div>
                      <p class="MsoNormal"> </p>
                    </div>
                    <div>
                      <p class="MsoNormal">Not that I know. </p>
                    </div>
                    <div>
                      <p class="MsoNormal"> </p>
                    </div>
                    <div>
                      <p class="MsoNormal">Chmouel.</p>
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </div>
          <br>
          _______________________________________________<br>
          Mailing list: <a moz-do-not-send="true"
            href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
          Post to     : <a moz-do-not-send="true"
            href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
          Unsubscribe : <a moz-do-not-send="true"
            href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
          More help   : <a moz-do-not-send="true"
            href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
          <br>
        </blockquote>
      </div>
      <br>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
Mailing list: <a class="moz-txt-link-freetext" href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a>
Post to     : <a class="moz-txt-link-abbreviated" href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>
Unsubscribe : <a class="moz-txt-link-freetext" href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a>
More help   : <a class="moz-txt-link-freetext" href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a>
</pre>
    </blockquote>
    As far as I know old URL rewriter works fine against Essex and it
    probably works with Folsom, so you should be able to easily replace
    the new URL middleware by the old one.<br>
  </body>
</html>