RSS feeds in the directory: 2794
Added today: 0
Added yesterday: 0
I don't really like instruments with a very high barrier to entry. Not because I can't work with them (I can), but because at some things the team spends far too much time.
I had heard about the security bundle and how it does not overpower the developers, but that was long ago. Over the last couple of years went Symfony 4, which is presented as a mega-easy and super-fast and security like changes a lot on the topic of simplification. But no, it turns out, much better not.
the Task — to close a URL on a simple basic authentication with a fixed username-password. Any users not in the project. Where can it be? Begin to look for, but there are only descriptions of how to do it when users are still there plus accepted answer on StackOverflow, which States that you can't do that.
that's it. Finish. The majority of this falls off because to go into the source code and spend time trying to understand how to write the config below, breaking through abstractions and by combining firewall, the provider and the encoder will be a very small number of developers.
security: providers: api_users_in_memory: memory: users: test: password: qwerty encoders: Symfony\Component\Security\Core\User\User: plaintext firewalls: api: pattern: ^/api stateless: true http_basic: provider: api_users_in_memory
Morality: flexible not that difficult to do. Just not easy to do.
RoboPHP in Kemerovo, report 30.01.2018 at 10:36
About the ethics of hacking 29.01.2018 at 15:41
Talk about safety in Kemerovo on RoboPHP 20.01.2018 at 23:32
DigitalOcean has increased the memory for$ 5 droplet twice 16.01.2018 at 21:59
2017 31.12.2017 at 00:51
Local domains 21.12.2017 at 00:01
Yii 2.0.13 03.11.2017 at 09:27
ProseMirror 16.10.2017 at 23:56
About the work and the balance 24.09.2017 at 13:20
En.rmcreative.ru 11.08.2017 at 10:50