scottklement.com

Issue resolved. Thank you!

- markl

This issue has been resolved. I had an error in the clientId. The web developer said he was sending a "Bad Request - ClientId/ClientSecret invalid." but I was only seeing "HTTP/1.1 400 Bad Request"

Now that the web service is returning the authorization token, I'm trying to use the YAJL DATA-INTO ...

This is a follow up post to the issue I was having with HTTPAPI. That issue has been resolved.

I have a simple authorization routine. I copied much of the code from the recent OATH2 post. I POST a clientId and clientSecret to a webservice and it returns an expires variable and an access token ...

Thank you for the response.

I did find a difference in case but that didn't make a difference - same error: HTTP/1.1 400 Bad Request

The unlink opcode is new to me. I misinterpreted one of the examples I was reviewing. They're for IFS files. I removed that code.

Any other suggestions?

After working with the authentication server web developer, we have determined that sending JSON to his authentication routine is not required. He was able to CURL and URL encode the variables to the server and retrieve the (JSON) security token. This is his CURL and JSON output which I'm attempting ...

New poster, long time RPG developer but somewhat new to interfacing with web servers. HTTPAPI_VERSION 1.48

I have a simple application that needs to POST a couple static JSON fields (or one JSON field with JSON formatting) to an authentication server which should retrieve a token if authenticated ...