I recently started working with Atmos and wrote an java class to extract recursively all metadata of files and directories stored in a certain namespace. Testing my implementation with the Atmos Online Service, it worked out fine. So, my next step was to try it out on my companies Atmos testing installation. Here the extraction fails with the following message:
/rest/namespace/test1/
x-emc-uid:myUsername
Hash: u25S8mUOOqi1+ADqMLV6l0UO7I8=
1032
There was a mismatch between the signature in the request and the signature computed by the server.
Reading through all discussions concerning the mismatch of signatures, it looks like that the Api fails to sign the request correctly. But I don't know why it works with the Atmos Online Service and not with my companies Atmos testing installation.
Please help me and give some advices or tips where I should start debugging.
Are you using the correct set of UIDs and shared secrets for the on-premise Atmos instance? There are no differences with regards to how requests are signed with Atmos Online vs. a private cloud instance of Atmos.
Can you try to access your on-premise instance with the AtmosFox plugin using the same UIDs and shared secrets that fail with your code?
I'm using AtmosFox to deploy my test data and metadata no matter if testing with the EMC Online Atmos instance or my private instance of Atmos. It works fine on both.
The error only happens when I run my source code on my private instance of Atmos. I'm sure of this behaviour, because I tested my source code first with the EMC online instance of Atmos. There everything works fine.
That's the reason, I'm so surprised about the error and have no answer, yet.
Dirk can you post a wireshark trace of your app running when it generates this error? what ersion of Atmos and what version of the wrappers are you using?
Trusting the error message is correct, I would recheck all the values used for signature calculation. With correct parameters supplied (uid/token, sharedkey) for your private Atmos, the Java code should take care of the signature. BTW, I use 1.3 and the Java code works fine. Signature calculation for REST W/S is documented in the Atmos Programmer's Guide. Please review that and see if you can debug/dump the values to determine the issue.
BTW, ensure the time on the client and the server are same. There is a 5 min time window. But if that is the problem then you will get a specific error.
rbala1
1 Rookie
•
222 Posts
540
0
Posted November 29th, 2010 06:00
Dirk,
Are you using the correct set of UIDs and shared secrets for the on-premise Atmos instance? There are no differences with regards to how requests are signed with Atmos Online vs. a private cloud instance of Atmos.
Can you try to access your on-premise instance with the AtmosFox plugin using the same UIDs and shared secrets that fail with your code?
Here's link to download the plugin for Firefox: https://addons.mozilla.org/en-US/firefox/addon/178414/
Raj