<div dir="ltr">These are two different clusters with their own individual auth systems. In fact, one is internal to where I work and another is at a customer site. These should both be using swauth and that let me to believe that both should have the same behavior.<div>
<br></div><div>I am using the jclouds java library. I am looking at the jclouds code to find out if there's some problem with the extra "v1.0". My hunch was that I should not use the "v1.0" in the endpoint url since jclouds seems to append it. But that didn't work. I'll update this thread if I find something in jclouds that is the problem.</div>
<div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 23, 2014 at 9:23 PM, Clay Gerrard <span dir="ltr"><<a href="mailto:clay.gerrard@gmail.com" target="_blank">clay.gerrard@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">ah ok, so are these two clusters setup as part of a single swauth installation? Are you using one as the auth system with service endpoints to the other (i.e. <a href="http://gholt.github.io/swauth/dev/api.html#set-service-endpoints" target="_blank">http://gholt.github.io/swauth/dev/api.html#set-service-endpoints</a>)?<div>
<br></div><div>Or are these two separate clusters which should be configured the same but seem to exhibit different behaviors based on the same input?</div><div><br></div><div>Also - what client? What is the auth url being given to it? Can you try to drop the v1.0? The /v1.0/v1.0 thing doesn't seem like it should work.</div>
<span class="HOEnZb"><font color="#888888">
<div><br></div><div>-Clay</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jan 23, 2014 at 4:12 PM, Shrinand Javadekar <span dir="ltr"><<a href="mailto:shrinand@maginatics.com" target="_blank">shrinand@maginatics.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Yes, swauth.</div><div><div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Thu, Jan 23, 2014 at 1:52 PM, Clay Gerrard <span dir="ltr"><<a href="mailto:clay.gerrard@gmail.com" target="_blank">clay.gerrard@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Is SwiftAuth... like Swauth?<div><br></div><div><a href="https://github.com/gholt/swauth/search?q=SwiftAuth&ref=cmdform" target="_blank">https://github.com/gholt/swauth/search?q=SwiftAuth&ref=cmdform</a><br>
</div><div>
<br></div><div>or something else???</div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Thu, Jan 23, 2014 at 10:44 AM, Shrinand Javadekar <span dir="ltr"><<a href="mailto:shrinand@maginatics.com" target="_blank">shrinand@maginatics.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr">Hi,<div><br></div><div>I am trying to debug a swift auth problem. There are two swift clusters using SwiftAuth for authentication.</div>
<div><br></div><div>On one cluster, when the client wants to authenticate, I see a GET request being sent to:</div>
<div><br></div><div><a href="http://swift.domain.com/v1.0/v1.0" target="_blank">http://swift.domain.com/v1.0/v1.0</a><br></div><div><br></div><div>along with the user-name and password. It receives a 200 OK from the server along with the X-Storage-Token and X-Auth-Token. The client is successfully authenticated and things work perfectly.</div>
<div><br></div><div>On the other cluster, when the client wants to authenticate, I see a GET request being sent to:</div><div><br></div><div><a href="https://swift2.anotherdomain.com/v1.0/v1.0" target="_blank">https://swift2.anotherdomain.com/v1.0/v1.0</a><br>
</div><div><br></div><div>along with the username and password. In this case, the client receives a 404 NOT FOUND response. If I use <a href="https://swift2.anotherdomain.com/v1.0" target="_blank">https://swift2.anotherdomain.com/v1.0</a>, things work fine.</div>
<div><br></div><div>Is there a config option in swift to either ignore the second "v1.0" in the path or maybe handle it in some other way so that the auth succeeds?</div><div><br></div><div>Thanks in advance.</div>
<div>-Shri </div></div>
<br></div></div>_______________________________________________<br>
Mailing list: <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
Post to : <a href="mailto:openstack@lists.openstack.org" target="_blank">openstack@lists.openstack.org</a><br>
Unsubscribe : <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>