Age | Commit message (Collapse) | Author | |
---|---|---|---|
2016-06-22 | [feature] expose is_admin in the user api | NavaL | |
So that whoever consumes the API can use this attribute to determine if admin functionalities should be made available to the current user. | |||
2016-04-11 | allow monitor auth to create users even if invites are normally required. | elijah | |
2016-04-01 | api: added super simple motd, closes #7866 | elijah | |
2016-03-30 | api: return proper 404 for GET /1/identities/:id.json | elijah | |
2016-03-30 | api: added json error pages, allow "." in the :id param of all api routes | elijah | |
2016-03-28 | api: added get(:show) to identities and users, allow monitors to ↵ | elijah | |
create/delete test & tmp users. | |||
2016-03-28 | api: added allow ability to limit what IPs can access api using a static ↵ | elijah | |
configured auth token. | |||
2016-03-28 | api tokens - clarify terms: "monitors" are admins that authenticated via api ↵ | elijah | |
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-28 | api tokens: allow for special api tokens that work like session tokens but ↵ | elijah | |
are configured in the static config, to be used for infrastructure monitoring. | |||
2016-03-19 | Handle conflict on token cleanup - fixes #7670 | Azul | |
the only race condition I can think of here is this... somebody tries to authenticate with a token that is almost expired. auth checks and notices it is not expired yet so starts to prolonge it. Before the polonged token is written to the db the cleanup script discovers that it has just expired. prolonged token is written to the db cleanup script fails to delete it from the db as it has been updated. So what we want in this case is to keep the token alive as it was renewed in the last minute. | |||
2016-02-10 | allow user accounts to be re-enabled, and for associated identities to also ↵ | elijah | |
get re-enabled. | |||
2016-01-31 | remove cert fingerprints for disabled users, so that they cannot send email ↵ | elijah | |
anymore. closes #7690 | |||
2016-01-16 | retain locale in URL when logging in and signing up, and ajax actions in ↵ | elijah | |
general. | |||
2016-01-14 | added UI for invite codes | elijah | |
2016-01-10 | highlight admin areas with caution tape (wip) | elijah | |
2016-01-10 | fix user list | elijah | |
2016-01-10 | Merge branch 'remove_couponcode' of ↵ | elijah | |
https://github.com/Alster-Hamburgers/leap_web into remove_couponcode # Conflicts: # lib/tasks/invite_code.rake | |||
2015-10-19 | [bug] Only show donation if payment present | Folker Bernitt | |
2015-10-19 | Merge pull request #198 from claucece/develop | azul | |
Braintree_implementation | |||
2015-10-19 | Merge pull request #196 from EvyW/develop | azul | |
Admin - Ability to enable/disable user | |||
2015-10-14 | Reverting submodule update | claucece | |
2015-10-13 | Remove Coupon Code gem and make invite code = id | ankonym | |
Id is set = invite code to make it easier to delete the invite codes that get created during the leap platform tests (because this avoids having to look up ttheir id each time). | |||
2015-10-13 | Replace Coupon Code gem for invite code creation | ankonym | |
Replacing the Coupon Code gem with base64/securerandom as suggested by Elijah. | |||
2015-10-13 | Remove Coupon Code gem and make invite code = id | ankonym | |
Id is set = invite code to make it easier to delete the invite codes that get created during the leap platform tests (because this avoids having to look up ttheir id each time). | |||
2015-10-13 | Replace Coupon Code gem for invite code creation | ankonym | |
Replacing the Coupon Code gem with base64/securerandom as suggested by Elijah. | |||
2015-10-13 | Fix the InviteCode initialize method so leap_web tests stay green | ankonym | |
2015-10-13 | Adjust the rake task to make id = invite code | ankonym | |
This will simplify invite code deletion after running tests. | |||
2015-10-06 | Integrated feedback on multi-invite codes | ankonym | |
Removing some superfluous code, mostly, and structuring tests better. | |||
2015-10-05 | deleted comment | claucece | |
2015-10-05 | add a comment regarding home | claucece | |
2015-10-05 | add subscriptions | claucece | |
2015-10-05 | changed routes and links | claucece | |
2015-10-05 | subscriptions, translation | claucece | |
2015-10-05 | subscriptions, haml and translations | claucece | |
2015-10-05 | added customers, recurring payment and payment_info | claucece | |
2015-10-05 | correctly set up comments | claucece | |
2015-10-05 | added payment_info, _customer_form, sucess instances | claucece | |
2015-10-05 | Donation button | claucece | |
2015-10-02 | Update rake task to allow generation of multi-use invites | ankonym | |
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.) | |||
2015-10-02 | Allow multi-use invite codes | ankonym | |
Introduce a invite_max_uses property to invite codes to allow admins to set a maximum number of uses for invite codes. | |||
2015-10-01 | identing 2 | EvyW | |
2015-10-01 | Identing first line | EvyW | |
2015-09-28 | with out identing | EvyW | |
2015-09-28 | Add localization labels to signup form and user.en.yml | ankonym | |
Added the necessary labels to allow the localization of the signup form and the labels to users.en.yml for localization | |||
2015-09-28 | changes style sheets | EvyW | |
removed the three last lines | |||
2015-09-28 | Make invite code configurable | ankonym | |
Through the config param 'invite_required', providers can decide whether users need to provide an invite code upon signup. The default setting is false. | |||
2015-09-28 | Cleaned up code in invite_code_validator.rb | ankonym | |
2015-09-28 | Fixed the signup bug that wrongly consumes the invite code. | Aya Jaff | |
2015-09-28 | Fixes for the invite code validator | ankonym | |
Validation should only happen for new records User invite code was nil for invalid invite codes Adding missing tests | |||
2015-09-28 | Make sure codes can only be used once, fix validations | ankonym | |
We introduced a count on invite codes to make sure that (at the moment) codes can only be used once. (The code will also allow multi-use codes in the future.) Also, some of our validations weren't validating against the correct data, which is now fixed. |