José Valim f26e6a269f Decouple serializers from Devise modules. You can use any serializer at any time, as long the API required by the serializer is satisfied. Since session serializer is encrypted, it simply stores the id and the resource klass. Cookie is not encrypted, so it creates a random token and store it in the database, so in order to do the token cleanup, you need provide remember_me! and forget_me! methods, as in :rememberable.		2009-12-20 12:31:02 +01:00
..
authenticatable.rb	Decouple serializers from Devise modules. You can use any serializer at any time, as long the API required by the serializer is satisfied. Since session serializer is encrypted, it simply stores the id and the resource klass. Cookie is not encrypted, so it creates a random token and store it in the database, so in order to do the token cleanup, you need provide remember_me! and forget_me! methods, as in :rememberable.	2009-12-20 12:31:02 +01:00
confirmable.rb	Added skip_confirmation! It skips confirmation token generation, e-mail sending and automatically sets confirmed_at.	2009-12-15 00:30:28 +01:00
recoverable.rb	Added skip_confirmation! It skips confirmation token generation, e-mail sending and automatically sets confirmed_at.	2009-12-15 00:30:28 +01:00
rememberable.rb	Decouple serializers from Devise modules. You can use any serializer at any time, as long the API required by the serializer is satisfied. Since session serializer is encrypted, it simply stores the id and the resource klass. Cookie is not encrypted, so it creates a random token and store it in the database, so in order to do the token cleanup, you need provide remember_me! and forget_me! methods, as in :rememberable.	2009-12-20 12:31:02 +01:00
session_serializer.rb	Decouple serializers from Devise modules. You can use any serializer at any time, as long the API required by the serializer is satisfied. Since session serializer is encrypted, it simply stores the id and the resource klass. Cookie is not encrypted, so it creates a random token and store it in the database, so in order to do the token cleanup, you need provide remember_me! and forget_me! methods, as in :rememberable.	2009-12-20 12:31:02 +01:00
timeoutable.rb	Rename :timeout to :timeout_in and release gem again.	2009-11-25 00:11:49 -02:00
trackable.rb	Added trackable for sign_in_count, sign_in_at and sign_in_ip.	2009-11-24 15:18:42 -02:00
validatable.rb	Send :scope to the proper validation.	2009-12-16 01:28:43 +01:00