| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When a user login using the form we know log an error level information with information about the user:
- username used
- IP
- User agent
For example:
> Authentication failure for user "eza", from IP "127.0.0.1", with UA: "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36".
It’ll allows server admin using fail2ban to configure it to block these people if they generate too much failure authentication.
|
| |
|
|
|
|
|
|
|
|
| |
While creating a new user using the API, we also create a new client for the current user.
So the app which just create the user can use its newly created client to configure the app.
That new client is only return after creating the user.
When calling the endpoint /api/user to get user information, the new client information won’t be return.
|
| |
|
| |
|
| |
|
|
|
|
| |
The Profile validation_groups does not exist and then for validation to be skipped (like password length)
|
|
|
|
|
|
| |
The only ugly things is how we handle error by generating the view and then parse the content to retrieve all errors…
Fix exposition fields in User entity
|
|
|
|
| |
Signed-off-by: Thomas Citharel <tcit@tcit.fr>
|
|\ |
|
| |
| |
| |
| | |
Fix #2933
|
| | |
|
| |
| |
| |
| | |
Signed-off-by: Thomas Citharel <tcit@tcit.fr>
|
| |
| |
| |
| | |
Signed-off-by: Thomas Citharel <tcit@tcit.fr>
|
| |
| |
| |
| | |
Signed-off-by: Thomas Citharel <tcit@tcit.fr>
|
|/
|
|
| |
Signed-off-by: Thomas Citharel <tcit@tcit.fr>
|
| |
|
| |
|
|\
| |
| | |
add translations/wallabag_user.de.yml (fixes #2673)
|
| |
| |
| | |
Wallabag->wallabag
|
| | |
|
| | |
|
| |
| |
| |
| | |
See https://github.com/FriendsOfSymfony/FOSUserBundle/blob/master/Upgrade.md\#200-alpha3-to-200-alpha4
|
| | |
|
| |
| |
| |
| |
| |
| | |
When resetting the password, the overriden template we used wasn’t well spelled.
And since we are using a locked version of FOSUser (on a custom commit), the translation of `resetting.check_email` is wrong in any language but english.
|
|\| |
|
| |\
| | |
| | | |
Translation update - French
|
| | | |
|
| |/
| |
| |
| |
| | |
We are injecting CraueConfig service when we only need to retrieve one or two values from it.
Instead I discovered we can directly inject a value from a service in the service definition!
|
| |
| |
| |
| | |
Fix #2062
|
|\| |
|
| |
| |
| |
| | |
add links on small screens
|
| | |
|
| | |
|
| |
| |
| |
| | |
PostgreSQL doesn’t like when we compare interger and boolean :)
|
| |
| |
| |
| | |
Added translations and documentation
|
| | |
|
|/ |
|
|
|
|
| |
Fix #2380
|
|
|
|
|
| |
When a user register itself AND the wallabag instance is configured to send a confirmation email, the user is disabled when the listener (which create the config) receive the event.
There were a check (don't know why) if the user is enabled we create the config. But the user is disabled when confirmation email is actived.
|
|
|
|
| |
To avoid some bad things to happen…
|
|
|
|
|
|
| |
- remove the “add a user” from the config page
- add a CRUD on user
- fix some missing translations (+ bad indentation)
|
|
|
|
|
| |
When a user register, the template displayed saying it should now check its email was misspelled.
Resulting in displaying the default one (with margin issue).
|
|
|
|
|
|
|
|
| |
Using a listener, user config is now created when a user:
- is created from the command line
- register (with or without email confirmation)
- is created from the config panel
|
|
|
| |
add missing "
|
|
|
| |
create wallabag_user.pl.yml file
|
|
|
|
|
| |
Instead of queing real Entry to process, we queue all the item to import from Pocket in a raw format.
Then, the worker retrieve that information, find / create the entry and save it.
|
|\ |
|
| |
| |
| |
| | |
Occitan translation, I hope I properly put it where it has to be.
If there reminds other textes to translate, please let me know!
|