single signon

I have a few questions on Drupal. i am evaluating it for my company and I keep getting stuck on 3 things.

1. How does drupal replicate content across multiple datacenters? If I have my authoring server in one location, how does the content and metadata stay in sync?

2. I need to use a single sign on solution. How would this work if none of the webservers are shared?

3. If I have content that is the same, can I share it between sites?

Thanks for your time.

Chris

Hello,

I'm just trying to get all information, spread out in different nodes and comments, together into one single post:

We implemented a OpenID single sign on solution for some of our clients (we call it Omniauth). It's based on Development Seeds great work on an OpenID Single Sign on solution for Drupal. Besides general improvement, instead of using feeds, foaf and PubSubHubbub to synchronize user information we used OpenID's own update_url (http://openid.net/specs/openid-attribute-exchange-1_0.html#fetch_request) and store_request (http://openid.net/specs/openid-attribute-exchange-1_0.html#store_request) to share user information between sites.

Omniauth includes the modules that are necessary, exported configuration into Features and installation profiles for both provider and relying parties.

I made a screencast to allow you to understand easier how to set up Omniauth and it's provided functionality at this moment: http://vimeo.com/xamanu/omniauth-drupal-openid-single-sign-on-solution

the single-signon options for mere-Drupal-mortals seem to be pretty thin, which is rather suprizing considering the flagship Drupal Gardens uses OpenID

I am looking at setting-up a network of sites within Aegir hosting and I've been spending a lot of time spinning my wheels with Bakery and OpenID type "solutions" - I've been annoying people and arguing and basically struggling through up the learning curve

We will have a wide variety of single-install Drupal sites, hosted under different domains, and possibly under different hosting locations.

Je voudrais mettre en place Drupal 6.16 avec le reverse proxy SSO Vulture et j'avoue ne trouver aucune aide sur le sujet.

Si quelqu'un a déjà expérimenté cette architecture merci de votre retour.

Hello all,

I am runnung a small network of multilanguage Drupal 5.16 sites using a single codebase, separate databases and instead of sharing users across databases I use a seperate user database that is accessed by all websites. The user database contains the following tables (these tables were dropped from the other databases):

• authmap
• buddylist
• buddylist_buddy_group
• buddylist_groups
• buddylist_pending_requests
• facebook_status
• privatmsg
• privatmsg_archive
• privatmsg_block_user
• privatmsg_folder
• sequences
• sessions
• userpoints
• userpoints_txn