Closed mitfik closed 11 years ago
This one is a huge step forward. We removed lots of unnecessary code and improved authenticators. Right now we can use multiply times the same class name in authenticators. It will be easier also to implement new settings and extend configuration for casserver. Also gives us possibility to have different config files for different servers. Right now we have just one but I already work on API server which soon will be ready.
One of the biggest change is the way how user configure authenticators right now we use just yaml array for storing all authenticators. For example:
authenticators:
- class_name
options1: 1
- class_name_2
options2: 2
I'm curious about backwards compatibility with the change to configuration options. I notice you've changed authenticator to authenticators, how will this work with existing deployments.
It will wont work with the existing deployments because of those changes. This is why I created new branch rubycas2.0 which will be next release candidate as soon as we will clean the code and implement all new features from TODO list. This one will not be merge into master branch.
Add sinatra contrib and use sinatra/config_file for handling config files.