v1.1.0

• Allow usage with devise 4.x (#50)
• Constrain sqlite3 gem version to match rails expected version (#51)

@cgunther

v1.0.2

Allow usage with devise 4.5 (@cgunther).

v1.0.1

Adds support for devise 4.4 and Ruby 2.5 (@paul).

v1.0.0

Changes the name for enabling HTTP Auth for the token strategy to adhere to the devise convention:

# initializers/devise.rb
Devise.setup do |config|
  # Before version 1.0.0
  config.http_authenticatable = [:token_options]
  # From version 1.0.0
  config.http_authenticatable = [:token]
end

Thanks @kassi!

v0.5.3

Adds support for devise 4.3.

v0.5.2

Adds support for devise 4.2 (@jankeesvw).

v.0.5.1

This release fixes an issue introduced in v0.5.0 which introduced token_expires_in. By default token_expires_in resulted in the need of an extra database table column on your model.

This release removes the need for the additional column if you do not set token_expires_in which is the default.

Thanks to @mikwat for the implementation and @leonelgalan for bringing this up.

v0.4.10

This release fixes an issue introduced in v0.4.9 which introduced token_expires_in. By default token_expires_in resulted in the need of an extra database table column on your model.

This release removes the need for the additional column if you do not set token_expires_in which is the default.

Thanks to @mikwat for the implementation and @leonelgalan for bringing this up.

v0.5.0

This is the first version that supports devise 4+. Besides that, there are no breaking changes compared to 0.4.9.

v0.4.9

This release supports devise 3.5.2 to 4.0 (not including).

It is a bugfix release which, however, introduces a breaking change. The configuration option expire_auth_token_on_timeout was removed as the previously introduced warden hook for timeoutable did not work as expected. In combination with the original devise warden hook for timeoutable the introduced hook for this gem got never called. This resulted in a never expiring authentication token. Confer the discussion.

With this release a new configuration option is introduced called token_expires_in. Confer the readme on how to use it. With this addition, you will need another datetime column in your model table called authentication_token_created_at which is used to store the time when an authentication token was created for a specific record.

Thanks a lot to @mikwat for bringing this up and working on a fix. Also, thanks to @lauraannwilliams for her initial idea.