Fog-aws not working with Hitachi #122
Comments
|
302s won't work because the path is of the canonical string used to calculate the HMAC address. we'd need a much more complex middleware to support this scenario. why are you getting redirects at all? is it not possible to use the correct url at initialization ? |
|
I tried specifying the URL given at 'Location:' response header (with and without the '/rest' ending) and I get the same redirection again and again (although I should not, as far as I know). However, the redirection is not likely to be "endless", because using the |
|
@palonsoro you might also try with |
|
Ok. I did try setting On the other hand, I did not know about the |
|
Hmm, I'm not sure beyond the port stuff. In particular I definitely wouldn't expect a redirect if you go directly to the location (which would be ideal since it would work around the signature issue). Could you run it with |
|
I am sorry for the delay. First: I have been able to avoid redirections by doing two things:
However, I still get 403 errors with valid credentials (at least, with credentials correctly working with CloudBerry client, for example). Here is the debug output produced when invoking If I have understood it well, it does list the containers but gets the error while trying to get information about particular containers, am I right? Thank you very much. |
|
I finally was able to get rid of 403. It was a permissions issue. I was given a minimum set of permissions that seemed not to be enough. So, as it has been a bit complicated to get this working, I am going to summarize everything we found (as well as some other things I found on my own previously) for future reference:
Thank you very much for your help. |
|
@palonsoro thanks for the summary doc. good luck! |
|
Thanks for the detailed report on what ended up working, glad to hear you found your way through. |
|
It was nice to see that Hitachi now allows you to register for a HCP trial - https://trycontent.hitachivantara.com/ While this thread has been helpful, I am adding some notes which hopefully will save someone's time. In order to make our application compatible with Hitachi Vantara, we had to make the following changes
|
|
@shrenuj-dm Glad you got this working and thanks for taking the time to share what you've learned with us! |
Good morning.
I have been trying to use fog to connect to the S3-compatible endpoint of an Hitachi instance and I get the following error (this comes from an
irbsession):It seemed that Excon was not following a 302 redirection. Thus, I did this:
So that
Excon::Middleware::RedirectFolloweris placed beforeExcon::Middleware::Expects.Then, the 302 response became a 403 forbidden, although I was providing good credentials (I triple-checked this). The full stack trace is:
Can you help me with this, please?
Thinking more in the future, is there any plan to natively support 302 redirections at fog out-of-the-box? I say this because, in my irb session, I can change the Excon defaults with no problem. But I need to do this kind of connection from a more complex program, which uses fog and only accepts a fog connection hash (and does not allow me setting anything else).
The text was updated successfully, but these errors were encountered: