Age | Commit message (Collapse) | Author | |
---|---|---|---|
2013-12-30 | Not actually how we want to do this, but at least finish outlined part, that ↵ | jessib | |
will later be replaced. | |||
2013-12-26 | Very very rough start to having messages for payment automatically created. | jessib | |
2013-12-24 | Catching some corner cases & new tests. | jessib | |
2013-12-24 | Add API tests and some refactoring of messages so we can get a user's ↵ | jessib | |
messages within the webapp. | |||
2013-12-24 | API method to mark a user's message as read (will refactor) | jessib | |
2013-12-24 | Initial start to messages API. | jessib | |
2013-12-23 | Merge remote-tracking branch 'jessib/feature/3389_download_links' into develop | Azul | |
Conflicts: core/app/views/common/_home_page_buttons.html.haml users/app/views/users/show.html.haml | |||
2013-12-22 | locale prefix support: | elijah | |
* set locale based on request header * enforce locale path prefix when current locale is not the default * note: don't use root_path anymore, instead use home_path | |||
2013-12-20 | enable billing engine by default, consolidate APP_CONFIG[:payments] and ↵ | elijah | |
APP_CONFIG[:braintree] into APP_CONFIG[:billing][:braintree] | |||
2013-12-19 | Put download link on user page. | jessib | |
2013-12-16 | Fix issue 4756: /login should not crash if one goes there when logged in. | jessib | |
2013-12-16 | Merge pull request #123 from azul/refactor/standartize-user-routes | jessib | |
refactor: remove Overview controller - we can use Users#show | |||
2013-12-13 | refactor: remove Overview controller - we can use Users#show | Azul | |
we were only using Users#show to redirect to the edit action. So I replaced that with the overview and we have no more use for the extra controller. This also simplifies linking to the users in question a lot. | |||
2013-12-13 | make the possible actions for users and admins configurable | Azul | |
with tests | |||
2013-12-13 | refactor: move edit sections into partials | Azul | |
2013-12-09 | Merge pull request #119 from jessib/feature/service_level | azul | |
Feature/service level | |||
2013-12-06 | make sure key responses are plain text | elijah | |
2013-12-06 | simple validation for pgp key format | Azul | |
2013-12-06 | ignore attempts to empty public_key, refactor | Azul | |
refactor: prepare validations of the uploaded pgp keys | |||
2013-12-05 | We won't want service levels in production mode, and have it so this initial ↵ | jessib | |
service level code won't break anything if it isn't set in the config. | |||
2013-12-03 | Some simplification of code. | jessib | |
2013-12-03 | Add ServiceLevel class to wrap config and give accessors. Has some hacky ↵ | jessib | |
parts, but seems like okay generic start for now. | |||
2013-12-02 | Merge branch 'develop' into feature/service_level | jessib | |
2013-11-26 | simple validation for pgp key format | Azul | |
2013-11-26 | ignore attempts to empty public_key, refactor | Azul | |
refactor: prepare validations of the uploaded pgp keys | |||
2013-11-25 | Give 404 error if one goes to /key/user for non-existing user. | jessib | |
2013-11-21 | Refactoring of code, and tests. | jessib | |
2013-11-18 | Need to cleanup some, but start to show public key for /key/username | jessib | |
2013-11-18 | Start of service level code, which will be tweaked | jessib | |
* stores desired & effective service level * whenever desired level is changed, effective level will be updated * allows user to set their desired service level * allow admin to update desired & effective service level | |||
2013-11-12 | Merge pull request #110 from azul/feature/cleanup-expired-tokens | jessib | |
Feature/cleanup expired tokens | |||
2013-11-08 | fix cornercase of non expiring tokens | Azul | |
2013-11-08 | Token.destroy_all_expired to cleanup expired tokens (#4411) | Azul | |
2013-11-06 | use the account lifecycle from UsersController#destroy | Azul | |
2013-11-06 | destroy all tickets created by a user when account is destroyed | Azul | |
In order to keep the users engine independent of the tickets engine i added a generic load hook to the account model. The tickets engine then monkeypatches the account destruction and destroys all tickets before the user is destroyed. The tickets are destroyed first so that even if things break there should never be tickets with an outdated user id. I would have prefered to use super over using an alias_method_chain but I have not been able to figure out a way to make account a superclass of the account extension and still refer to Account from the users engine. | |||
2013-11-05 | Identity.destroy_all_disabled will clean up disabled identities | Azul | |
This is mostly for cleaning up after tests so far. But we might expand this to destroy all identities disabled before a certain date. | |||
2013-11-05 | disabled identities to block handles after a user was deleted | Azul | |
2013-11-05 | refactor: Identity.disable_all_for(user) on user destruction | Azul | |
This way the identity model defines how identities should be disabled. We currently still destroy them. But it will be easy and nicely isolated to change this next. | |||
2013-10-30 | notify user their account was successfully deleted (refs #4216) | Azul | |
Also fixes a cornercase when admins deleted their own account. So far they would be redirected to the users list - which then refused access. Now they'll be redirected to the home landing page as well. | |||
2013-10-28 | Fix button to enable account: https://leap.se/code/issues/4246 | jessib | |
2013-10-28 | reset button loading... state on error (#4231) | Azul | |
including test refactored error display some | |||
2013-10-18 | Merge pull request #98 from jessib/feature/billing-past-due-subscriptions | azul | |
Feature/billing past due subscriptions | |||
2013-10-17 | Merge pull request #102 from azul/feature/3602-email-blacklist | jessib | |
blacklist system logins for aliases and logins | |||
2013-10-17 | blacklist system logins for aliases and logins | Azul | |
We blacklist based on three things: * blacklist in APP_CONFIG[:handle_blacklist] * emails in RFC 2142 * usernames in /etc/passwd The latter two can be allowed by explicitly whitelisting them in APP_CONFIG[:handle_whitelist]. We stick to blocking names that have been configured as both blacklisted and whitelisted - better be save than sorry. | |||
2013-10-17 | use latest version of srp_js to fix #4002 | Azul | |
We were not encoding the srp password properly before. So umlauts in the password would cause the login procedure to fail. | |||
2013-10-01 | Allow admins to view past-due subscriptions. | jessib | |
2013-09-26 | Since local part of email is case sensitive, want to allow remote email ↵ | jessib | |
addresses with uppercase letters in local part. | |||
2013-09-25 | visual feedback when submitting forms (#3164) | Azul | |
This also helps with the failing integration test. We needed a way to tell the ajax request was back. Observing the button state now works for that. | |||
2013-09-24 | use token auth when accessing the api from webapp | Azul | |
One failing integration test still needs to be fixed | |||
2013-09-23 | This ensures that email addresses contain only lowercase letters, and that ↵ | jessib | |
an identity's destination is a valid Email. | |||
2013-09-19 | Merge branch 'develop' into feature/only_lower_case_aliases | jessib | |