I'm trying to build a service that talks JSON to a program. I've built a simple module, and I can run basic queries. The problem is that my API key settings are ignored. I can change the nonce parameter without changing the hash, and the request still succeeds. I can also run queries an hour after they've been created, with the old timestamp (or with a randomly modified timestamp). Same thing with the domain, it makes no difference.
What's more, I get the hash, nonce, domain, and timestamp passed into my function when I have API keys activated. I don't get what I'm supposed to do with this information there, do I need to check these things manually?
I'm using the JSON server and Services, nothing else. I would appreciate it if somebody could help me with this. Also, a working example using API key authentication would be appreciated. All the examples I've seen turn off the keys in the first step, or use user login instead of API keys.
Comments
Comment #1
marcingy commentedMoving to json sever as xmlrpc server has no issues like this.
Comment #2
eagereyes commentedSame thing happens in Services when I do it from the services UI: my simple service that concatenates the first two arguments returns the domain and hash concatenated, not the the actual arguments.
My installation is a very basic Drupal with no external modules other than Services, API Key auth, the node service, and my test module.
Comment #3
eagereyes commentedPicked the wrong version, sorry. It's not the beta.
Comment #4
gddPlease go to I have tested this in multiple configurations and not only can I not replicated it, I'm having a really hard time seeing how it would be possible. This is almost ceratinly a problem with your service or (in the case of the first poster) with JSON Server. If you want to post your service (the service definition and the function) please do. I'm not sure how up to date the docs are right now, but use existing services as samples.
Comment #5
marcingy commentedchanging type and status
Comment #6
marcingy commented