By default, devise_cas_authenticatable uses "user" from the Ticket to load the User from the database. Across our apps, our Users are linked by a common id, not by username. This change allows devise_cas_authenticatable to be configured to use a value other than "user" in the Ticket. The client can set "cas_user_identifier" to a field that appears in cas_extra_attributes. devise_cas_authenticatable will use this value when finding the user.
Replace with "sqlite" See this friendly message from the sqlite team: Hello! The sqlite3-ruby gem has changed it's name to just sqlite3. Rather than installing `sqlite3-ruby`, you should install `sqlite3`. Please update your dependencies accordingly. Thanks from the Ruby sqlite3 team! <3 <3 <3 <3
…get an application and is not authorized. It was interesting that even the tests had an unnessecary step of clicking the 'here' link in the default device templates to get around this problem. In the event there is a infinite redirect loop, this needs terminated on the cas server and not the cas client.