Drupal Services module: Getting the API key or kid of the requester

The services_keyauth_get_kid() function.

I'm currently in the process of building a module to work with Analytics SEO. This module connects to Analytics SEO via the Services module. There has been some debate as to how to manage permissions. The 'correct' way is to log the user in and then use the usual Drupal access permissions system which would be great but I really don't like the way you submit the password in plain text.

My suggestion is to bind a user to the API key id (kid) although for a lot of people having a user per API key isn't needed or would be overkill - The services module works really well with anonymous calls, or key restricted function calls. But when different people are using the same functions with sensitive data there has to be a proper way of securing the data. The answer as I've suggested is to tie it all up with the API key or kid as it's stored in the database.

I spent several hours, trundling through Google and the module code itself before finally stumbling upon services_keyauth_get_kid(). Finally! I don't know why this was so hard to find, probably because it's quite easy to write your own function to query the database against the domain, but again I didn't want to do that because I was sure there would be some function that would do all of the security stuff for you:

services_keyauth_get_kid()

For those of you that are interested, I'm aiming to make this THE SEO module for Drupal. Yes there are other modules out there but they either don't do much, don't give ongoing analysis or are a pain to install. I'm pretty excited to be building this module because it will incorporate the best of both worlds: The awesome power of Analytics SEO with all its crawling, site audit to check all your pages, keyword and competitor analysis together with the advantages of being hooked right into your site e.g. to automatically analyse your page when you save it, suggest content changes and compare it against competitors, all in a well organised manner to make it quick to optimise your site.

Post new comment

By submitting this form, you accept the Mollom privacy policy.

User login

Author of...

  • http://t.co/oHKBnJn Dratman 13 years 35 weeks ago
  • 3 mobile email support not very fast! "We’ll get back to you within ten days" 13 years 36 weeks ago
  • Just learned about the great advantages of 'Using Per-Table Tablespaces' for innodb mysql tables. goo.gl/Xm8KZ Reclaiming disk space & more 13 years 36 weeks ago
  • Oooh, Amazon Kindle cloud reader: http://t.co/RYRLw68 13 years 37 weeks ago
  • Just pointed out to my boss: "You spelt 'gobbledegook' wrong." 13 years 38 weeks ago
  • OMG! opening <div>s in various files, and closing </div>s in various other files! Time to clean that up! 13 years 39 weeks ago
  • How come only now after all these years am I using the #Drupal format_plural() and Drupal.formatPlural() functions? 13 years 39 weeks ago
  • Why do I see so much custom #drupal code with comments such as: "Sorry I had to do it like this because Drupal won't do it" Yes it will! 13 years 40 weeks ago
Oliver Polden