By wulff on

I'm in the process of setting up Drupal for use as a CMS and community system for our university department.

I'm trying to set up a single sign-on system (like the one described in http://lists.drupal.org/archives/drupal-devel/2004-07/msg00737.html) to make it easy to create per-project and per-class Drupal sites.

Am I correct in assuming that the following tables are the ones who need to be in the global/shared database?

  • authmap
  • locales_meta
  • locales_source
  • locales_target
  • permission
  • profile_fields
  • profile_values
  • role
  • sequences
  • sessions
  • users

The message linked to above seems to refer to an older version of the database schema.

Comments

moshe weitzman’s picture

moshe weitzman commented

the tables which need to be shared depend on what you are trying to share and what you want separate. The email message to which you've linked tries to share users and permissions but not roles. that is, users can have different roles in each site, but the meaning of each role is consistent. that may or may not be what you want.

in general, you list of tables looks good. are you having specific troubles?

wulff’s picture

wulff commented

in general, you list of tables looks good. are you having specific troubles?

No problems yet, I just wanted to make sure I was sharing the right set of tables.

I think I'm trying to achieve the same thing you mentioned in the e-mail: A central set of users with different roles on a number of Drupal sites (one Drupal site per class and individual Drupal sites for staff projects).

The biggest challenge so far has been finding a way to use Drupal to manage our static content (the main site: http://www.tem.dtu.dk/). I've solved it by modifying the book.module and creating a 'book' for each content area -- so far everything works great!