| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Feature: Token based auth
|
|
|
|
|
|
This way the failed stubbing errors were more telling
|
|
This way we can stub the token to return the user directly. Stubbing User.find_by_param is not a good idea as it will make all calls to User#find_by_param with a different id fail.
|
|
So far we allow two mechanisms of authentication:
* session based
* token based
If token fails session will be atempted in most cases. So we can't just redirect here or we get a double render error.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
[ci skip]
|
|
|
|
|
|
Test updating user password through api
|
|
use the same login validations on sessions and users
|
|
|
|
That's the only meaningful response.
|
|
The session ones were outdated so valid usernames could not login if they contained a '.'
Refactored so both models use the same module for this validation to ensure consistency.
|
|
|
|
|
|
|
|
Key must end in _html so the html doesn't get escaped.
|
|
|
|
Per ISEC informational issue, manually set the private property only in ...
|
|
disable, must remove billing engine from Gemfile (and re-bundle)
|
|
an admin.
|
|
|
|
fix billing tests to use user id with customer resources
|
|
cases where it is an admin who set it.
|
|
|
|
I think this is very confusing and should be changed to:
resource :users do |user|
user.resource :customer
end
|
|
Read Braintree config from file
|
|
Feature/identity rewrite
|
|
user variable, due to complication that an admin might be accessing data for another user.
|
|
This can be set per environment and also is not tracked in git
|
|
|
|
|
|
|
|
edit for other users.
|
|
|
|
|
|
Conflicts:
app/views/home/index.html.haml
|
|
|
|
customer.
|
|
|
|
|
|
|
