CHANGELOG 17 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354
  1. === 1.1.3 :: In progress...
  2. * CHANGED:
  3. * XML responses now start with a correct XML declaration specifying UTF-8 encoding
  4. (<?xml version="1.0" encoding="UTF-8" ?>).
  5. * FIXED:
  6. * Extra attributes with UTF-8 characters should be correctly encoded under ruby 1.8.7.
  7. * Improved compatibility with various versions of ActiveRecord, ActiveSupport and
  8. other dependencies.
  9. * Minor code reorganization and cleanup.
  10. === 1.1.2 :: 2012-09-19
  11. * FIXED:
  12. * Upgraded sinatra-r18n dependency to 1.1.0. This should fix localization issues
  13. for some users.
  14. === 1.1.1 :: 2012-06-08
  15. * NEW:
  16. * Google authenticator now has a "restricted_domain" option to allow logins only
  17. from Google accounts (email addressed) under a specific domain name.
  18. * FIXED:
  19. * When installed as a gem, localization should now work correctly thanks to fixed
  20. translations path.
  21. === 1.1.0 :: 2012-04-19
  22. * NEW:
  23. * Localization is now done using R18n instead of Gettext.
  24. * Restored compatibility with Sinatra 1.2
  25. * Now compatibile with Ruby 1.9.3
  26. * Can now run without Bundler if all required dependencies are already installed.
  27. * es_AR translations.
  28. * CHANGED:
  29. * It is no longer possible to select the locale by adding a 'lang=xx' attribute to the
  30. request URL. The locale is selected using the 'Accept-Lanuage' header sent in the
  31. request. However the old 'lang' functionality may be restored in a future version.
  32. * Certain localized string keys have changed. If you are using your own custom views
  33. you may need to modify them accordingly.
  34. * FIXED:
  35. * Removed unnecessary bcrypt requirement for encrypted sql authenticators.
  36. * Single Sign Out requests should now work with SSL-enabled services.
  37. === 1.0.1 :: 2011-11-22
  38. * NEW:
  39. * On startup the server now checks for a config.yml file in its own root directory,
  40. then in /etc/rubycas-server.
  41. * FIXED:
  42. * Compatibilty with Sinatra 1.3 (:public changed to :public_folder).
  43. * Database migration files should now be correctly bundled with the gem distribution.
  44. * Should work with both ActiveRecord >= 2.3.12 and < 3.1. Previously the dependency
  45. was erronously set to accept only the 2.3.12 series.
  46. * Specs now pass under ActiveRecord 2.3.12 in both Ruby 1.8 and 1.9
  47. === 1.0.0 :: 2011-08-03
  48. * NEW:
  49. * Rewrite to replace Camping/Picnic with Sinatra
  50. * Support for Ruby 1.9.2
  51. * Support for Active Record 3
  52. * CHANGED:
  53. * Google authenticator proxy configuration has been changed (see config.example.yml)
  54. === 0.8.0
  55. * NEW:
  56. * Support for localization via Ruby-GetText.
  57. See http://code.google.com/p/rubycas-server/wiki/Localization
  58. for details. [antono]
  59. * Switched to Picnic 0.8.x, so RubyCAS-Server is now based on Rack
  60. and Camping 2.0 and is now compatible with Passenger Phusion
  61. * Change to authenticator API: every authenticator now has a class 'setup'
  62. method that gets called at server startup. This is where class-level
  63. configuration should be done (e.g. establishing a database connection).
  64. This is different from the 'configure' method which gets called on a per-
  65. instance basis for each authenticator. [godfat]
  66. * Database connections are now automatically released back to the connection
  67. pool at the end of each request. This should allow the server to handle
  68. many more concurrent requests, since database connections are no longer left
  69. checked out of the pool.
  70. * Added new SQL authenticator (sql_rest_auth) compatible with the
  71. restful_authentication Rails plugin. [antono]
  72. * Re-licensed under the MIT License.
  73. * FIXED:
  74. * Fixed weird problems with loading controllers when using older versions of
  75. activesupport and/or rubygems.
  76. * Failure to connect to a service during a single sign out request is now
  77. handled gracefully.
  78. * Required gem dependencies have been re-enabled in the gemspec.
  79. * Authlogic authenticator files added to gemspec. [rajiv]
  80. * Authenticators are now instantiated on a per-request basis (rather than
  81. once at startup) to ensure thread safety.
  82. === 0.7.1 :: 2008-11-10
  83. * Fixed dependency loading problems introduced by upstream changes in RubyGems
  84. 1.3.1.
  85. === 0.7.0 :: 2008-11-04
  86. * NEW:
  87. * Implemented single-sign-out functionality as specified in CAS 3.3. See
  88. http://www.ja-sig.org/wiki/display/CASUM/Single+Sign+Out.
  89. * It is now possible to configure Authenticators to return extra attributes
  90. to CAS clients alongside the username. For an example of how to do this see
  91. the included SQL authenticator. Also have a look at:
  92. http://groups.google.com/group/rubycas-server/browse_thread/thread/5eade3793cb590e9
  93. Note that extra attributes of type other than String or Numeric are serialized
  94. into YAML format before being sent along to the client.
  95. * Added an MD5-password version of the SQL authenticator for Drupal and any other
  96. database that stores its passwords in hashed form (thanks malcolmm).
  97. * Added new Google authenticator for authenticating against Google/GMail
  98. accounts.
  99. * CHANGED:
  100. * Service URIs are now automatically normalized. For example, if the service
  101. URI given to the server has a 'ticket' parameter, the ticket will now be
  102. automatically stripped. This is to avert any possible issues raised by
  103. misbehaving CAS clients (the CAS ticket should never be part of the service
  104. URI). Same goes for other CAS-related parameters like 'service', 'renew',
  105. and 'gateway'. Additionally, the trailing '/' and '?' characters are
  106. automatically stripped from URLs, since, for example, "http://google.com/"
  107. is almost certainly equivalent to "http://google.com".
  108. * The expire_sessions config variable is now respected -- ticket granting
  109. ticket cookies are set with an expiry datetime, so that the SSO session
  110. is effectively terminated once the ticket_granting_ticket_expiry period
  111. is reached.
  112. * If present, the HTTP_X_FORWARDED_FOR header is used for recording the
  113. client's address. This is useful when the server is running behind a reverse
  114. proxy, but it should not be considered authoritative since it can be
  115. easily spoofed.
  116. * The 'service' field in the 'casserver_st' table has been changed from
  117. VARCHAR(255) to TEXT in order to accomodate service URIs longer than 255
  118. characters (fixes issue #46).
  119. * The CAS XML responses are no longer whitespace-formatted (i.e. Markaby's
  120. auto-indentation has been turned off). Apparently the whitespace was
  121. causing problems with mod_auth_cas. See:
  122. http://groups.google.com/group/rubycas-server/browse_thread/thread/e482fe09999b73d3
  123. * When used without pre-authentication, the LDAP authenticator now tries to
  124. bind by searching for the given username in the LDAP directory based on the
  125. configured username_attribute. Prior to this change the authenticator
  126. attempted to bind with the LDAP server by assuming that the username credential
  127. matches the user's CN. This is no longer the case.
  128. * CAS responses to invalid requests (for example where required parameters
  129. are missing or incorrect) will now have HTTP status code 422. Internal server
  130. errors (where the server rather than the client is at fault) have error 500.
  131. Previously most responses had error code 200, regardless of their contents.
  132. * FIXED:
  133. * Fixed logout action to work properly with ActiveRecord 2.1 (eager loading behaviour
  134. was changed upstream forcing a change to the way we look for ProxyGrantingTickets
  135. to delete on logout).
  136. * When running under Mongrel, the USR2 signal should now restart the server as
  137. expected -- however currently this only works when the server is running
  138. in the foregaround. When daemonized, USR2 will shut down the server without
  139. restarting (see issue #58).
  140. * Fixed activerecord/activesupport gem load problems, hopefully once and for all
  141. (however picnic-0.7.0 is now required).
  142. === 0.6.0 :: 2008-03-28
  143. * Much of the supporting functionality that makes RubyCAS-Server
  144. act as a well-behaved Linux service has been abstracted out
  145. into its own library. This new library is called Picnic and is
  146. now a gem dependency for RubyCAS-Server. You can find out more about
  147. it at http://code.google.com/p/camping-picnic/.
  148. * The logout action will now accept a 'destination' parameter in lieu of
  149. 'service'. This means that if a 'destination' parameter is given with
  150. some URL, the logout action will show the login form, allowing the user
  151. to immedietly log back in to the service specified by 'destination'.
  152. * The logout action will now accept a 'url' parameter. If given, the logout
  153. page will show a message indicating that the CAS session has been terminated
  154. and instructing the user to click on a link to follow the given URL. If the
  155. 'url' parameter is given, the login form will NOT be shown on the logout
  156. page (see above).
  157. * When an authentication failure occurs (because the user submitted
  158. invalid credentials or the login ticket is missing), the server
  159. now returns a 401 (Unauthorized) response instead of 200.
  160. * An encryption-enabled version of the SQL authenticator is now
  161. available. For more info have a look at:
  162. http://code.google.com/p/rubycas-server/wiki/UsingTheSQLEncryptedAuthenticator
  163. * Better compatibility with Oracle databases. The database migration
  164. no longer tries to create tables with long names when long
  165. table names are not supported by the underlying database connector
  166. (issue #15).
  167. * The server now automatically removes leading and trailing whitespace from
  168. the username entered by users. Passwords however are left intact, with no
  169. whitespace removed.
  170. * The server can now be configured to automatically downcase the
  171. username entered by users (dowcase_username option). So if a user
  172. enters "JSmith", the system will convert it to "jsmith" if the
  173. downcase_username option is set to true.
  174. * The server can now be made to bind to a specific address. See the
  175. :bind_address option in the config.example.yml file.
  176. * Fixed bug with ActiveRecord 2.0.2 where service tickets were not
  177. being given a type (issue #37).
  178. === 0.5.1 :: 2007-12-20
  179. * Tickets generated by the server should now be a lot more secure.
  180. The random string generator used for generating tickets now uses
  181. Crypt::ISAAC. Tickets have also been extended in length; STs, PTs
  182. and LTs can now extend up to 32 characters, and PGTs and PGT-IOUs
  183. up to 64.
  184. === 0.5.0 :: 2007-09-20
  185. * Gateway requests should now be handled correctly. When the request to the
  186. login page is made with gateway=true as one of the parameters, the CAS
  187. server will immediately redirect back to the target service along with
  188. a service ticket if an SSO session exists for the user (or without a
  189. service ticket if there is no pre-existing SSO session).
  190. Note that if you are using RubyCAS-Client and want gatewaying, you will
  191. need to upgrade it to 1.1.0 as gatewaying was broken in prior versions.
  192. * If gateway=true is specified as part of the logout URI, the server will
  193. log the user out and immediately redirect them back to the specified
  194. service. In other words, you can now do "gatewayed logouts" as well
  195. as logins.
  196. * A login ticket can now be remotely requested from the server by placing
  197. a POST request to '/loginTicket'.
  198. * The login view can now be made to return only the login form. This is
  199. done by adding the 'onlyLoginForm' parameter to the '/login' request.
  200. Optionally, a 'submitToURI' parameter can be supplied to force the login
  201. form to submit to the given URI (otherwise the server will try to figure
  202. out the full URI to its own login controller). This functionality may be
  203. useful when you want to embed the login form in some external page, as
  204. an IFRAME otherwise.
  205. * Custom views can now be used to override the default Markaby templates
  206. by specifying a 'custom_views_file' option in the configuration. See
  207. custom_views.example.rb. [jzylks]
  208. * Table names have been shortened to work with Oracle. A migration has
  209. been added that should do the shortening for you the first time you run
  210. this new RubyCAS-Server version.
  211. * Multiple authenticators can now be specified. During authentication,
  212. credentials are presented to the first authenticator, then the second,
  213. and so on, until the user is validated by any one authenticator or fails
  214. validation for all of them. [jzylks]
  215. * When using webrick, you can now run with SSL disabled by omitting the
  216. ssl_cert and ssl_key parameters.
  217. * Changed incorrect MySQL example database configuration -- option should
  218. be 'host:' not 'server:' (issue #22).
  219. === 0.4.2 :: 2007-07-26
  220. * The LDAP/AD authenticator has been largely re-written. The code is a bit
  221. cleaner now, and should work better with non-Active Directory LDAP servers
  222. (although this has yet to be tested since I don't have access to a non-AD
  223. LDAP server).
  224. * The validate() method in your authenticators now receives a :service element
  225. (in addition to :username, and :password). This is simply the service
  226. url (if any) specified in the user's CAS request. If you call
  227. read_standard_credentials(credentials) at the top of your validator, the value
  228. will also be available as @service along with @username and @password.
  229. * By request, a :username_prefix option has been added to the ldap
  230. configuration. If entered, this string will be automatically prefixed to
  231. the username entered by the user.
  232. * A bug having to do with handling authenticator errors has been fixed.
  233. Any authenticator error messages should now be correctly shown on the
  234. login page.
  235. * Minor improvements to error messages having to do with login tickets.
  236. They're a bit more prescriptive now, explaining to the user what steps
  237. they should take to correct the error.
  238. === 0.4.1 :: 2007-06-07
  239. * This release restores compatiblity with older versions of rubygems
  240. (pre-0.9.0). To achieve this, we alias the 'gem' method to the old
  241. 'require_gem' if 'gem' is not already defined.
  242. * rubycas-server-ctl will now quiety delete an orphaned .pid file
  243. instead complaining loudly and refusing to start up.
  244. * Fixed minor bug in rubycas-server-ctl that sometimes incorrectly reported
  245. startup problems when in fact the server had started just fine.
  246. === 0.4.0 :: 2007-06-05
  247. * Added rubycas-server-ctl script for controlling daemonized server.
  248. * rubygems-0.9.0 or later is now required.
  249. * Added system startup script to be used in /etc/init.d on Linux systems.
  250. * Authenticator can now be loaded from an external file using the 'source'
  251. configuration option.
  252. * Better preemptive detection of startup problems with mongrel.
  253. * User now sees an error message if the service URI is not a valid URI (i.e.
  254. if it's not URI-encoded or otherwise malformed).
  255. === 0.3.0 :: 2007-03-29
  256. * Fixed glaring security problem with LDAP/AD Authenticator where under some
  257. circumstances blank passwords were accepted as valid.
  258. * Autocomplete has been turned off on the password field for better security.
  259. In the future we may allow autocomplete to be re-enabled using a
  260. configuration setting.
  261. * When the user visits the login page and is already authenticated (i.e. they
  262. have a valid ticket granting cookie), a message is shown at the top
  263. indicating that they are already logged in.
  264. * sqlite3-ruby is no longer required by the gem as a dependency. The user
  265. must now install it manually prior to installing rubycas-server. The
  266. building of sqlite3 native extensions appears to be somewhat flakey
  267. and probably defeats the original purpose of using it (which was
  268. to have a CAS server up and running with no additional DB configuration).
  269. We will use MySQL as the default database adapter instead, since it does
  270. not require additional libraries and many users will have a MySQL server
  271. already available.
  272. * Fixed bug that was causing all proxy-granting tickets to be deleted whenever
  273. any user logged out. Only the PGTs for the user that is logging out are now
  274. being deleted.
  275. * Trailing slashes in service URLs are now ignored when validating service
  276. and proxy tickets (e.g. "http://www.google.com" and "http://www.google.com/"
  277. are now considered to be the same service URL).
  278. * Authenticators now raise AuthenticatorError exceptions when encountering
  279. a problem/error. This makes it easier to send feedback to the user.
  280. However, other exceptions should still be raised when errors ought
  281. not be recoverable (i.e. programming errors).
  282. * Fixed serious vulnerability in LDAP authenticator where under some
  283. cirumstances the user could just enter '*' as their username to match
  284. any username. The LDAP authenticator will now refuse to process logins
  285. with usernames that contain the characters * ( ) \ / and the NULL
  286. character \0.
  287. * Views are no longer xhtml-validated. Markaby's auto-validation was turned
  288. off to allow for use of the autocomplete property on inputs, since this is
  289. the only viable way of turning off password storage in IE and Firefox at
  290. the page level.
  291. * You can now limit the maximum length of a login session by setting the
  292. expire_sessions config setting to true.
  293. * Fixed some minor bugs in the login view.
  294. === 0.2.0 :: 2007-03-20
  295. * ruby-casserver now behaves more like a real command-line app, accepting
  296. various command line arguments including -h (help), -v (version), -c (use
  297. an alternate config.yml), and -d (daemonize, when using webrick or mongrel
  298. mode).
  299. * Special characters in CAS XML responses are now properly encoded into XML
  300. entities
  301. * CAS XML responses are no longer auto-indented... Markaby's indentation
  302. seemed to be causing problems with the PHP CAS client.
  303. * Misc minor bug fixes/cleanup.
  304. === 0.1.0 :: 2007-03-01
  305. * First public release.