Age | Commit message (Collapse) | Author |
|
|
|
This avoids overwriting the PROVIDER_JSON constant in the
StaticConfigController and thus fixes test warnings.
Also moved away from using instance variables in the
ControllerExtension::JsonFile - instead querying the corresponding
functions now - less sideeffects and easier stubbing.
|
|
rails 4 mixes model, controller and integration tests. So lets
give this one a better name
|
|
This way the changed flash hash still is recognized.
Also changed the generic 'no_such_thing' i18n key to more specific 'no_such_user'.
The former is very hard to translate as the gender of thing may affect the translation of the 'no such' part.
|
|
|
|
|
|
|
|
|
|
create/delete test & tmp users.
|
|
configured auth token.
|
|
get re-enabled.
|
|
anymore. closes #7690
|
|
Admin - Ability to enable/disable user
|
|
|
|
|
|
|
|
|
|
https://github.com/azul/leap_web into develop
|
|
There are some places where we only want to require login unless you can use EIP anonymously. So far we had an anonymous_certs_allowed? method in all these controllers. Now it's replaced with ApiController#anonymous_access_allowed?. The naming better reflects that there might be other services that allow anonymous use at some point.
This also fixed a typo name -> @filename that broke the ConfigsController.
|
|
includes test
|
|
|
|
|
|
|
|
- default is true
- See issue #5217
- See companion change in leap_platform.
|
|
There's an identities tab now for admins that will allow unblocking blocked handles. It should be easy to expand for aliases and forwards and other types of actions such as editing.
|
|
hash token with sha512 against timing attacs #3398
|
|
|
|
|
|
We create them. let's reflect that in the verb.
|
|
|
|
|
|
Ticket.is_creator_vlidated? now actually fetches the user from the db and returns false if it does not exist.
|
|
cost -> rate
quota -> storage
|
|
The changes to the configuration required some non minor changes to the platform and also added some flexibility we don't require yet - and thus some new possibilities for errors.
So instead we still use the allow_..._certs and ..._cert_prefix options.
They basically provide the framework in which service levels can operate.
The service level configuration will not include the cert prefix anymore.
It only states if the service level is rate limited or not.
This avoids conflicts between the two configuration options.
I also removed the anonymous service level entirely.
It was also turning a boolean decision (do we provide anonymous eip or not) into something way more complex. Instead I added the AnonymousServiceLevel class to handle the corner cases for people who are not logged in.
Furthermore i renamed the UnauthenticatedUser to AnonymousUser so it matches the Anonymous Service Level nicely. It's also shorter and more intuitive.
|
|
|
|
Null Pattern for current_user - use it to get rid of some conditionals
|
|
:api/service will return a hash of the current users service level
This is failiing if the user is not logged in. Instead it should return the service description for an anonymous user.
|
|
cleaned up all the engine stuff that was never really used.
Afterwards there is not that much left that makes it into the toplevel.
|
|
|
|
response headers (in particular, 'X-Minimum-Client-Version'). It must now be placed in config/provider/provider.json
|
|
|
|
|
|
we're merging repositories into one
|