leap_web.git/test/unit, branch version/0.8

allow monitor auth to create users even if invites are normally required.

2016-04-11T21:10:38+00:00

api tokens - clarify terms: "monitors" are admins that authenticated via api token, "tmp" users are users that exist only in tmp db, "test" users are either tmp users or users named "test_user_x"

2016-03-28T23:03:54+00:00

api tokens: allow for special api tokens that work like session tokens but are configured in the static config, to be used for infrastructure monitoring.

2016-03-28T23:03:54+00:00

allow user accounts to be re-enabled, and for associated identities to also get re-enabled.

2016-02-10T18:56:57+00:00

remove cert fingerprints for disabled users, so that they cannot send email anymore. closes #7690

2016-01-31T23:10:10+00:00

Integrated feedback on multi-invite codes

2015-10-06T11:27:32+00:00

Removing some superfluous code, mostly, and structuring tests better.

Update rake task to allow generation of multi-use invites

2015-10-02T18:58:29+00:00

The rake task now takes a second (optional) argument that sets the number of uses per invite code.
If this is omitted, the default number of uses is 1.

(This commit also contains some minor code cleanup that removes some stuff that I'd commented out but not removed.)

Allow multi-use invite codes

2015-10-02T14:51:57+00:00

Introduce a invite_max_uses property to invite codes to allow admins to set a maximum number of uses for invite codes.

Make invite code configurable

2015-09-28T13:12:46+00:00

Through the config param 'invite_required', providers can decide whether users need to provide an invite code upon signup.
The default setting is false.

Removed the view_by__id from invite code test

2015-09-28T13:12:46+00:00