OTDS Auth via API questions

Hi -

Trying to get the basic auth flow working via API. I have been working with the following process flow:
1 - /otdsws/rest/authentication/credentials
2 - /otdsws/rest/authentication/ticketforuser

unfortunately I am getting an error when passing the ticket from the first call to the second:

{
  "status": 1009,
  "error": "Invalid parameter"
}

weird quoting on the web so I'm doing this again...

{ "status": 1009, "error": "Invalid parameter" }

I had this working when using a ticketforresource call but it was with a hard-coded resourceID.

I'm wondering if I have missed something obvious or if I am misinterpreting the meaning of the endpoints. Any suggestions would be appreciated.

Thanks!

Find more posts tagged with

API

Comments

Marius Bakkeli

Hi,

Did you solve this?
I'm getting the same error.

Regards
Marius

Tom Stratton

I was told by OT that the APIs to allow this are private/internal but that they are contemplating opening them up in a future release. We ended up having to regress to using OTDS local auth for the API login (total pain in the behind ;-)

Marius Bakkeli

Hehe, ok

Thanks for taking the time to reply!

Regards
Marius