I released an administrator plugin for PunBB earlier this week and Rickard has posted it on the PunBB Downloads page (about 3/4ths of the way down).

User Merge. Created by Terrell Russell. The User Merge plugin allows administrators to merge two user accounts.

This follows the Broadcast Email plugin from a couple years ago…

Broadcast Email. Created by trel1023. The Broadcast Email plugin allows administrators to broadcast e-mail to all registered users via the administration interface.

This post is about getting single-sign-on to work with a PunBB forum inside your Ruby on Rails application. I wanted to have a user who signs into the Rails app be ‘logged into’ the forum as well. This requires setting the cookie in the same way the PunBB code does it.

I have put this code in the bottom of my application.rb, so that it can be called from anywhere in the Rails app. I would suggest setting the cookie on login and clearing it on logout.

The forum config regex is based on the configuration parser in the PunBB SDK for Rails. It parses your existing PunBB cookie_name and cookie_seed from the PunBB install so you only need to keep that information in one place (PunBB).

The necessary php_serialize.rb file also comes from the /lib directory of the PunBB SDK plugin and is courtesy of Thomas Hurst (also available directly). It should be copied/placed into your own Rails app’s /lib directory and ‘require’d accordingly. The line below ending in \\ indicates a forced linewrap – and should be pulled back into a single line if you copy and paste this code.

  def set_shared_cookie
    # this is the punbb cookie
    # should be called on login from main site
    # the wiki uses the same cookie
    # setting it here allows unified login
    require 'digest/md5'
    forumconfig = get_forum_config_data() # private method at bottom
    # get forumuser info and set cookie
    forumuser = Forumaccount.find_by_username(@current_user.login)
    cookies[forumconfig[:cookie_name]] = {
      :value => PHP.serialize([forumuser.id, \\
         Digest::MD5.hexdigest("#{forumconfig[:cookie_seed]}#{forumuser.password}")]),
      :expires => 1.year.from_now
    }
  end

  def clear_shared_cookie
    # should be called on logout from main site
    require 'digest/md5'
    forumconfig = get_forum_config_data() # private method at bottom
    # set cookie for Guest
    cookies[forumconfig[:cookie_name]] = {
      :value => PHP.serialize([1,Digest::MD5.hexdigest("#{forumconfig[:cookie_seed]}Guest")]),
      :expires => 1.year.from_now
    }
  end

  # Uses regex to parse the php punbb config file
    # ahgsoftware.com/punbb_sdk/
    # make sure the config file exists
    # make sure 'RewriteEngine Off' is in /forum/.htaccess and wiki/.htaccess
  def get_forum_config_data
    config_hash = Hash.new
    c = File.read(File.join(RAILS_ROOT,'public/forum/config.php'))
    c.scan(/\$(\w*)\s*=\s*['"](.*)['"];/).each do |pair|
      config_hash[pair[0].to_sym] = pair[1]
    end
    return config_hash
  end

Of course, keeping your users in sync across the main Rails app and the Forum install is its own trick – and necessary before the above cookie injection will work. I’ve got Theforum and Forumaccount models that are wired to the PunBB database. I keep the usernames and passwords synced whenever users/passwords are created/deleted/updated.

database.yml

theforum_production:
  adapter: mysql
  database: punbb_production
  host: localhost
  username: xxxxxxxxx
  password: xxxxxxxxx

theforum.rb

class Theforum < ActiveRecord::Base
  self.abstract_class = true
  establish_connection "theforum_#{RAILS_ENV}"
end

forumaccount.rb

class Forumaccount < Theforum
  set_table_name :users

  def encrypt_and_save_new_password(password)
    write_attribute("password", self.sha1hashed(password))
    save
  end

  def sync_from_account(account)
    write_attribute("email", account.email)
    forumname = account.prefix+" "+account.first_name+" "+account.last_name
    write_attribute("realname", forumname)
    save
  end

  protected

  def sha1hashed(str)
    Digest::SHA1.hexdigest("#{str}")[0..39]
  end

end

A separate trick was to make DokuWiki look for and pay attention to the PunBB cookie we created at the beginning of the post. I got that for free with the shipping auth options in Dokuwiki. I simply pointed my Dokuwiki install at the PunBB install and the magic was complete.

Success: A login to the Rails app also sets a cookie for PunBB which is fully honored by Dokuwiki.

An additional benefit is now the entire site is under one codebase and can be installed/developed without moving as many pieces around.

I wanted to manage a group of users and passwords for a community with an existing Ruby on Rails application – and then have both a PHP-based PunBB forum and PHP-based wiki running inside the Rails app. Of course, more interestingly, I wanted to make the sessions and cookies all align and share a single sign-on.

And this past week, I poked enough at the right pieces to make it happen.

I first found this post at macdiggs.com but found the solution to lack directory mapping in addition to allowing the PHP to execute inside the Rails /public/ directory. I wanted http://example.com/forum to render and not throw a Rails error. As it stood, only http://example.com/forum/index.php and URLs like it would come up correctly.

Then, I started seeing references to turning off Apache’s RewriteEngine…

The solution I’ve now got in place has two parts:

1) Edit the Apache configuration file for your virtualhost. This tells Apache not to push any requests that start with /forum or /wiki to the Rails app (here, a mongrel cluster) – and to just handle them by itself (via the PHP processor).

RewriteEngine On
# send all /forum traffic to php
RewriteCond %{REQUEST_URI} ^/forum.*
RewriteRule .* - [L]
# send all /wiki traffic to php
RewriteCond %{REQUEST_URI} ^/wiki.*
RewriteRule .* - [L]
# Redirect all non-static requests to cluster
RewriteCond %{DOCUMENT_ROOT}/%{REQUEST_FILENAME} !-f
RewriteRule ^/(.*)$ balancer://mongrel_cluster%{REQUEST_URI} [P,QSA,L]
<Proxy balancer://mongrel_cluster>
BalancerMember http://127.0.0.1:6000
BalancerMember http://127.0.0.1:6001
</Proxy>

2) Add/Edit the .htaccess file in both the forum and the wiki directories. This tells any requests that were sent the way of either the forum or the wiki to halt the rewriting engine and just process the requests themselves.

RewriteEngine Off

Now, both http://example.com/forum and http://example.com/wiki render correctly.

As for getting the cookie to sync – please see my next post…

P.S. And now for all the phrases that I couldn’t find anywhere when I was looking for how to make all this magic happen – maybe someone else will find this stuff here: PHP within Rails, PHP inside Rails, PunBB in Rails app, Ruby on Rails, DokuWiki, PHP/Rails integration, PHP integration with Rails