Hello,
My question is essentially the same as this one, resolved on command line now, but seen again within PDI
"error":"client_too_new" attempting to get authentication token
I did execute the curl command on this same machine (windows) using cygwin successfully. Could the way I'm feeding the headers and parameters be my problem?
I've attached my transformation with the url and credentials redacted for anyone who might want to give it a try.
Sorry, I have not done any development or experimentation with the HCP-AW APIs. I am just a humble user. I haven't seen this error.
Hmm, let me ask in a different way as I'm starting to think that the "version_mismatch" error I'm getting is a red herring and what is it actually trying to tell me is that I'm mis-configured somewhere.
The curl command looks like this
curl https://<my url>/fss/public/login/oauth -iku "<my username>:<my password>" -H "Content-Type: application/x-www-form-urlencoded" -H "Accept: application/json" -H "X-HCPAW-FSS-API-VERSION: 3.0.3" -d "grant_type=urn:hds:oauth:negotiate-client”
My curl query has 3 headers
and one piece of data
My generate rows step looks like this:
While my Rest Client Step looks like this:
On the command line I have been able to replicate an status of "version_mismatch" if I misspell one of the header parameters. So perhaps I'm inadvertently doing the same here?
Hi Roguen,
I guess I am not doing something right as well.
Please check my screen below and see the response I get.
I notice that in this example you appear to have encoded the username and password. And that is what you would do if you were making a call against HCP's APIs (base64 and md5sum). But in this case the username and password are plaintext and you're getting back a token for subsequent calls being made.
Someone please correct me if I'm wrong about that, but that's what I see in the documentation here: http://hitachi-data-systems.github.io/anywhere-fss-sdk/fss-api-doc/#FSSAPI/authentication/fssapi-authIntro.htm%3FTocPath…
I also notice that the AW version you're using is pretty dated: 2.1.1
Would you be able to use a more recent version of the software at all?
As a gut check, I know you're using a browser tool here. Perhaps Chrome's REST API tool, and it is a good one, I use it myself. Could you try making the same call via a command line curl statement though? Personally I sometimes find that this gets everything clear and on one page for me. In your screenshot for instance I can see the one tab, but would actually expect your authorization to be on the authorization tab.
Finally, I would suggest making anew question for this. Mine was marked as resolved, and so less folks are likely to look at it. You can do a hyperlink reference from your question to this one to provide additional information, but it keeps it focused on what you need.
I don't use this step, but...
I believe that "Application Type" refers to how you are sending the data, not what you are willing to get back.
So I think you would want "FORM URLENCODED" rather than JSON
Similarly, if you make the field grant-type the full body of the request (grant_type=urn:hds:oauth:negotiate-client) and supply that as the Body Field
This should really leave you with two headers that you are manually adding: Accept and X-HCPAW-FSS-API-VERSION
Also remember to turn logging up to "Debug(Row Level)" and look at what is happening. It often provides really good clues.
Thanks Gotn O'Guts,
After some trial and error your suggestions were able to resolve my issue.
What I changed:
Without these changes I would get either a version mismatch (version wasn't the issue, so this was a red herring as I suspected) or a incorrect call which unfortunately is too ambiguous to point at anything.
Logging was also a big help here.
on Feb 14, 2018
I don't use this step, but...
I believe that "Application Type" refers to how you are sending the data, not what you are willing to get back.
So I think you would want "FORM URLENCODED" rather than JSON
Similarly, if you make the field grant-type the full body of the request (grant_type=urn:hds:oauth:negotiate-client) and supply that as the Body Field
This should really leave you with two headers that you are manually adding: Accept and X-HCPAW-FSS-API-VERSION
Also remember to turn logging up to "Debug(Row Level)" and look at what is happening. It often provides really good clues.