Tree: 68f407c632

for_activeadmin

get_specs_running

master

list

v1.1

v1.1.1

v1.1.2

v1.1.3

v1.1.4

v1.1.5

v2.0

v2.0.1

v2.1.0

v2.1.1

v2.2.0

version

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '68f407c632'

${ noResults }

Commit Graph

4 Commits (68f407c632a840c4eddd2d74b583e06e061db2a9)

Author	SHA1	Message	Date
Sam Clegg	eed1bf62a1	Add support for directly delivered OTP codes ... Direct OTP codes are ones that are delivered directly to the user (e.g. SMS) via send_two_factor_authentication_code. These are randomly generated, short lived, and stored directly in the database. TOTP (and the rotp gem) is now only enabled for those user that have a shared secret (user.create_otp_secret).	9 years ago
Moncef Belyamani	d2b6d39d24	Add support for OTP secret key encryption ... **Why**: To provide an additional layer of security. The TOTP spec (RFC 6238) recommends encrypting the keys. http://tools.ietf.org/html/rfc6238 **How**: Borrow the encryption code from the `attr_encrypted` gem and use it to encrypt and decrypt the `otp_secret_key` attribute. Allow users to add encryption by passing in `encrypted: true` to `has_one_time_password`. This provides backwards-compatibility for existing users of the gem. See the README updates for more detailed instructions for both new and existing users.	9 years ago
Dmitrii Golub	6610f83335	update rspec to version 3	11 years ago
Edger	a8cea83253	is_fully_authenticated helper	11 years ago