"synchronizing" users across applications

[jsuggs]

I am working on a startup site (http://www.murmp.com still working on the backend, so don't judge by its looks). I wanted to create a blog (and eventually a forum as well) to be able to communicate and interact with my users. I chose s9y since it was able to support postgres as the backend database.

I'm about to start digging through all of the code, but wanted to see if anyone else had already done this (hate to reinvent the wheel) or just has some insight.

Basically I would like for my users to have a single login that will give them access to their account but also have that automatically create a login for the blog as well (or vice-versa). I would really like to write some triggers that just handle the changes, so that if they update their password (or any other "common" field) then the changes update all of the different pieces of software. I don't know if this would be easiest to accomplish by writing triggers and stored procedures, or if it should be handled at the application level (php).

Ideally, everything (ids, etc) would stay the same and be a seamless integration. Logging into the application logs you into the blog, updating, logging out, etc.

[garvinhicking]

Hi!

Sadly I'm no Postgresql-User. But I know that with MySQL you could setup VIEWS that target a single user database. You simply map the user databases of all applications to one central table, and all others are only views...

It would be hard to do that at application level, that would mean tearing out a lot of code of all involved applications...

Regards,
Garvin