<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Re-sending to list, since I think I've got this by mistake:<br>
<br>
On 05/24/2012 12:42 PM, Kuo Hugo wrote:
<blockquote
cite="mid:CA++_uhtK3S+e2pPcdGMBrgk4YqmyHb8iuDyOM28ZPFRCqHHN-A@mail.gmail.com"
type="cite">
<div style="text-align:left"><font color="#222222" face="arial,
sans-serif"><span style="font-size:14px;white-space:nowrap"><b>Thanks
for all . </b></span></font></div>
<div style="text-align:left"><font color="#222222" face="arial,
sans-serif"><span style="font-size:14px;white-space:nowrap"><b><br>
</b></span></font></div>
<div style="text-align:left"><font color="#222222" face="arial,
sans-serif"><span style="font-size:14px;white-space:nowrap"><b>I
checked several parts of legacy_auth. </b></span></font></div>
<div style="text-align:left">
<font color="#222222" face="arial, sans-serif"><span
style="font-size:14px;white-space:nowrap"><b><br>
</b></span></font></div>
<div style="text-align:left"><font color="#222222" face="arial,
sans-serif"><span style="font-size:14px;white-space:nowrap"><b>There're
some requirements of legacy_auth. We do not want to hack
exist essex code though. </b></span></font></div>
<div style="text-align:left"><font color="#222222" face="arial,
sans-serif"><span style="font-size:14px;white-space:nowrap"><b><br>
</b></span></font></div>
<div style="text-align:left"><font color="#222222" face="arial,
sans-serif"><span style="font-size:14px;white-space:nowrap"><b>We're
considering to add a filter in keystone's pipline. While
the API point to /v1.0 . Route to /v2.0/tokens . And
transfer incoming headers to a json format. </b></span></font></div>
<div style="text-align:left"><font color="#222222" face="arial,
sans-serif"><span style="font-size:14px;white-space:nowrap"><b>After
that , the middle-ware retrieve token and swift-proxy
public_url transfer into </b></span></font></div>
<div style="text-align:left"><font color="#222222" face="arial,
sans-serif"><span style="font-size:14px;white-space:nowrap"><b>X-AUTH-TOKEN</b></span></font></div>
<div style="text-align:left"><font color="#222222" face="arial,
sans-serif"><span style="font-size:14px;white-space:nowrap"><b>and </b></span></font></div>
<div style="text-align:left"><font color="#222222" face="arial,
sans-serif"><span style="font-size:14px;white-space:nowrap"><b>X-Storage-Url </b></span></font></div>
<div style="text-align:left"><font color="#222222" face="arial,
sans-serif"><span style="font-size:14px;white-space:nowrap"><b>return
to user. </b></span></font></div>
<div style="text-align:left"><font color="#222222" face="arial,
sans-serif"><span style="font-size:14px;white-space:nowrap"><b><br>
</b></span></font></div>
<div style="text-align:left"><font color="#222222" face="arial,
sans-serif"><span style="font-size:14px;white-space:nowrap"><b>But
there's still has an issue. what should be the tenant of
/v1.0 request? </b></span></font></div>
<div style="text-align:left"><font color="#222222" face="arial,
sans-serif"><span style="font-size:14px;white-space:nowrap"><b><br>
</b></span></font></div>
<div style="text-align:left"><font color="#222222" face="arial,
sans-serif"><span style="font-size:14px;white-space:nowrap"><b>In
Legacy_AUTH , the user's default tenant associate with
user under Users table. </b></span></font></div>
<div style="text-align:left"><font color="#222222" face="arial,
sans-serif"><span style="font-size:14px;white-space:nowrap"><b><br>
</b></span></font></div>
<div style="text-align:left"><font color="#222222" face="arial,
sans-serif"><span style="font-size:14px;white-space:nowrap"><b>Should
we keep this method , or pick up the first one tenant of
user from Essex's metadata table?</b></span></font></div>
<br>
</blockquote>
<br>
</body>
</html>