With multiple simultenous users logging in, the database pool size is getting exhausted. For a example a test using the default pool size settings with 3 concurrent users easily ends with:

ActiveRecord::ConnectionTimeoutError: could not obtain a database connection within 5 seconds. The max pool size is currently 5; consider increasing it.

    /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:198:in `checkout'
      /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:184:in `loop'
      /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.3/lib/active_record/connection_adapters/abstract/connection_pool.rb:184:in `checkout'
      ...
      /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.3/lib/active_record/base.rb:613:in `find'
      /usr/lib/ruby/gems/1.8/gems/activerecord-2.3.3/lib/active_record/base.rb:1900:in `find_by_ticket'
      /home/URBACON/mzukowski/eclipse-workspace/rubycas-server/lib/casserver/cas.rb:166:in `validate_service_ticket'

Most likely this is an issue with Camping or Picnic, but there may be something going wrong in the RubyCAS-Server codebase.

Just a heads up... it looks like running rubycas-server-ctl stop doesn't shut down the server as expected. I don't have time to look into this right now, so some help would be appreciated. The problem likely lies in Picnic rather than in RubyCAS-Server.

Here's my patch:
http://github.com/godfat/rubycas-server/commit/f4e0baf22924994b24d402ece2f8847277546eaf
I hope this could be considered. :)
Thanks!

See http://groups.google.com/group/rubycas-server/browse_thread/thread/707d81a7fe002024?hl=en

Ex:
http://example.com?foo=1
and
http://example.com?foo=2
both refer to the same service, yet ServiceTicket.matches_service? would incorreclty identify them as different services.

Need to modify ServiceTicket.matches_service? (lib/casserver/models.rb:65) so that URL parameters are stripped off both URLs being compared.

Currently there's only one session lifetime, i.e.

#maximum_session_lifetime: 172800

in the config file, and cookies['tgt']'s "expires"
is set according to this value, and there's no
expired time saved in database.

This make doing "Remember me on this computer" hard,
since we need to track at least two different session lifetime.
The easy way is just adding another config option, e.g.

#remember_me_session_lifetime: 864000

and setup cookies['tgt']'s "expires" according to whether user
checked the checkbox of "Remember me on this computer".

I would go to this approach due to my limited time,
working on my fork. Feel free to cherry-pick or apply
on your own with other editing and/or refactoring.

On the other hand, I am thinking of the possibility of adding
expired_at in database, then we could omit this config,
simply adding more time to "expires", enforcing session
expires time at server side for more security, customizing
more expiration policy, etc, etc.

Many thanks for your listening.

I've translated from English to Tradition Chinese,
which is spoken here in Taiwan.
http://github.com/godfat/rubycas-server/blob/master/po/zh_TW/rubycas-server.po
This is based on my master fork, so line numbers would be
a bit different, and there's an additional:
msgid "Remeber me on this computer"

I don't know why but Firefox send HTTP header Accept-Language
with zh-tw instead of zh-TW, and en-us instead of en-US.
I am not sure if this should be case-sensitive or case-insensitive.
FWIW, here's the patch to make it work.
http://github.com/godfat/rubycas-server/commit/eb3108a8b9ca2ce46959669411e44437bd028c5e

The google auth plugin MUST support captcha as logins fail if google (randomly) decides it needs one.

Actually, SQLAuthenticator has the code in validate method. However, unfortunately, it has been missing in validate method in SQLEncryptedAuthenticator.

Working from the head release at github, on Mac OS X, I did the following:

1. Uninstalled all rubycas-server gems
   
2. Run rubycas-server/bin/rubycas-server
   
3. Set the config.yml file it generated to use the CASServer::Authenticators::Test
   
4. Run rubycas-server again
   
5. Attempt to login using username = test, password = testpassword

Expected: Login to work
Actual: Received the following exception -

NoMethodError: undefined method `merge' for nil:NilClass
    /Users/myusername/projects/rubycas-server/lib/casserver/controllers.rb:136:in 'post'
    /Users/myusername/projects/rubycas-server/lib/casserver/controllers.rb:133:in 'each'
    /Users/myusername/projects/rubycas-server/lib/casserver/controllers.rb:133:in `post'

Looking at the code it appears as though this may be related to the changes that make Authenciators configure on every request. The same config.yml file works fine with the last known gem (gunark-rubycas-server-0.8.0.20090812) which predates the Authentication changes I believe.

For reference, here is the entire config.yml file.

server: webrick
port: 443
ssl_cert: /Users/myusername/projects/rubycas-server/demo.pem

database:
  adapter: mysql
  database: casserver
  username: root
  password: 
  host: localhost

authenticator:
  class: CASServer::Authenticators::Test

theme: simple
organization: CAS
infoline: 
default_locale: en

log:
  file: /var/log/casserver.log
  level: INFO