AnsweredAssumed Answered

API call for Token is unsuccessful

Question asked by Roguen Keller Employee on May 1, 2018
Latest reply on May 2, 2018 by Roguen Keller

Branching this question off of Chika Emeka-Nweze's question in this thread

Version Mismatch When Making REST Client Call to HCP-AW

 

Based on that conversation I suggested that the next step be to run a curl command first get that working.

 

curl https://<your URL>/fss/public/login/oauth -iku "<your pain text username>: <your pain text password>" -H "Content-Type: application/x-www-form-urlencoded" -H "Accept: application/json" -H "X-HCPAW-FSS-API-VERSION: 2.1.1” -d "grant_type=urn:hds:oauth:negotiate-client"

 

I've highlighted the portions of this that need to be filled in.

Something I would like you to do with this is type it all in, do not copy and paste because a lot of times the quotation marks do not come over as they should.

 

If that still doesn't work then please post up your error message.  I can say definitively that for my version of AW, 3.0.3 this call works.  So if this does not get back the token then:

  • We have the wrong URL
  • We have the wrong username/password
  • Quotation marks are not being interpreted correctly
  • Something else is wrong with the version 2.1.1 that you are using.  I would suggest an update for this if possible anyway.

Outcomes