If you try to do this by parsing URLs you could end up with a big mess and some serious security issues. A better solution, if CF supports it, would be to move authentication to LDAP (or, conceivably, OpenID). Then, in your LDAP server, you define who has access to what. The users have a single sign-on that enables them to visit these two components and any new ones that are added later, as you set permissions in one place. We haven't yet implemented it, but it looks as though there is an LDAP module that plays nicely with Drupal 5.3; worth doing, if, as I said, CF can also support LDAP for authentication, and you can set up the LDAP server (openLDAP?)
ari
On 10/31/07, Chris McCreery chris.mccreery@gmail.com wrote:
Thanks Gwen only issue is that the site the users will be logging in to originally is a coldfusion site and not another Drupal site. Would either of these allow this?
On 10/31/07, Saint-Genest Gwenael gwenael.saint-genest@makina-corpus.com wrote:
Hi,
Maybe you can try with FierceSSO [1] or CAS [2] . I've not testedthis two modules but this seems to be a good entry point for your problem :)
Gwen
[1] http://drupal.org/project/fierce_sso [2] http://drupal.org/project/cas
Chris McCreery wrote:
I am working on a project of integrating Drupal with an existing site
that
has a members login, the drupal site would only be accessible by
members
that have logged into the main site. So for instance:
User accesses www.site.com Logs in to members only site Now can access the drupal site drupal.site.com
My question is what is the best way to do this, we don't want users to
log
in twice, or to have to recreate the users in drupal each time a new
user
registers on the main site.
Thanks
-- Saint-Genest Gwenael < gwenael.saint-genest@makina-corpus.com> Makina Corpus - http://www.makina-corpus.com/
-- [ Drupal support list | http://lists.drupal.org/ ]
-- Chris McCreery -- [ Drupal support list | http://lists.drupal.org/ ]