CiviCRM Community Forums (archive)

Xavier, I agree with the bug! I will raise an issue :-) (and assign it to......... )

See, the patch welcome joke is not as funny when you are on the other side of it

The question that is still open to me is that I am not clear about the login function. You mentioned it is no longer required and that still confuses me. Or maybe better said: that would be really undesirable behaviour...

I'm not clear as how to use it. The session is a pita to deal with, keep expiring on you when you have long running inactive users...

I think you are saying that you can use any api_key with the REST as long as the api_key exists somewhere in the contact database, am I right? So I could create a user called John Doe with api_key 'testJD' . Anyone accessing that Civi install with the REST (entity=Contact, action=Get, array('version'=>3,key='<sitekey>',api_key='testJD') will get data, even if they never used a login and are not John Doe. Is that correct?

It must exist at least one(one different user per rest consumer is my recommendation).

You must use all the time key & api_key for each rest request.

Second question: I DO still need the site_key too, right?

indeed, it must exist and it's unique and you need to use it in conjonction with api_key.

Am I clearer now?