On Fri, 2008-25-01 at 16:41 -0800, AD. wrote:
> On Jan 25, 12:13 pm, "Thomas G. Willis" <[EMAIL PROTECTED]> wrote:
> > Yep, this is why I love drupal and tolerate php. :)
> 
> Haha - my thoughts exactly.
> 
> I've never hacked around with Drupals session and auth stuff before,
> but I do have a few Drupal modules under my belt (including one hosted
> on drupal.org).
> 
> Although I've been following TG development since about 0.8 or so I've
> yet to do anything serious with TG. But I'd be keen to help you guys
> where I can with getting TG and Drupal to interoperate better - that
> way I might find more uses for TG.
> 
> Another possibility...
> 
> hook_auth can be used by a module to handle remote apps authenticating
> against Drupal via XMLRPC:
> http://api.drupal.org/api/function/hook_auth/5
> 
> Note: this isn't secure if you don't trust the remote site. The
> upcoming Drupal 6 has scrapped this in favour of OpenID - which opens
> up a bunch of new interoperability opportunities anyway. Drupal 5 has
> an OpenID module available too (http://drupal.org/project/openid)
> although I haven't used it.

Thanks Anton, I'll check out the open ID module. It doesn't look ( on
further reading ) like it should be too hard to share auth, the session
id for the cookie in drupal is stored sensibly and accessible fairly
cleanly ( I think! ). I think if I can figure out how to get and stash
the entire incoming request that would be helpful. ( Especially for
working with TG2 and Ian's wicked cool WebOb stuff. ) I think I will try
going both ways and see what I can come up with. I'll certainly write
any findings here.

Iain



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to