Age | Commit message (Collapse) | Author |
|
if doc.keys has not been set doc.keys[pgp] will raise an error.
We always upload the key after signup - but this might fail and there is some time in between. Not checking for this condition lead to errors in the couch logs.
|
|
The datastructure changes to that email_aliases is not available on the user record anymore.
Keeping these views leads to errors on couch servers.
|
|
Conflicts:
core/app/views/common/_home_page_buttons.html.haml
users/app/views/users/show.html.haml
|
|
* 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
|
|
APP_CONFIG[:braintree] into APP_CONFIG[:billing][:braintree]
|
|
|
|
|
|
refactor: remove Overview controller - we can use Users#show
|
|
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.
|
|
with tests
|
|
|
|
Feature/service level
|
|
|
|
|
|
refactor: prepare validations of the uploaded pgp keys
|
|
service level code won't break anything if it isn't set in the config.
|
|
|
|
parts, but seems like okay generic start for now.
|
|
|
|
|
|
refactor: prepare validations of the uploaded pgp keys
|
|
|
|
|
|
|
|
* 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
|
|
Feature/cleanup expired tokens
|
|
|
|
|
|
|
|
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.
|
|
This is mostly for cleaning up after tests so far. But we might expand this to destroy all identities disabled before a certain date.
|
|
|
|
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.
|
|
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.
|
|
|
|
including test
refactored error display some
|
|
Feature/billing past due subscriptions
|
|
blacklist system logins for aliases and logins
|
|
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.
|
|
We were not encoding the srp password properly before. So umlauts in the password would cause the login procedure to fail.
|
|
|
|
addresses with uppercase letters in local part.
|
|
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.
|
|
One failing integration test still needs to be fixed
|
|
an identity's destination is a valid Email.
|
|
|
|
|
|
|
|
LoginFormatValidation. However, this is not how we will want it eventually.
One issue is that the errors messages are set on login, rather than the appropriate field.
|
|
|