Symfony 5 Security / Authentication Tutorial 

Great to hear...cheers Jason 👍

Thanks a lot...maybe some day!

Thanks a lot..much appreciated..and thanks for watching!

Maybe for S6...I should have used the new auth system for this series really

@@GaryClarkeTech I'll stick on symfony v5.2.99 for know then even though this video is a value for junior devs like me who is new on symfony. Thanks for your effort.

@@happysongs1802 Glad I can help 👍

Skondensowana wiedza to co przekazuje Ryan w SymfonyCasts ;D

@@garethfoxtrot5722 Możliwe, SymfonyCast dawno temu oglądałem :D

@@pawecyrklaf4729 ja to co jakiś czas wracam i oglądam materiały aby zobaczyć co nowego przygotowali ;) aczkolwiek już po kilku latach pisania w Symfony, więcej się czerpie z dokumentacji i stackoverflow ;D

@@garethfoxtrot5722 Mam dokładnie tak samo, jak coś szukam to dokumentacja lub stackoverflow, bo w tych kursach nie ma rzeczy, które po kilku latach pisaniach są nowością :D

@@garethfoxtrot5722 Ogólnie to nic szałowego tam już nie ma, dobre miejsce dla kogoś kto dopiero zaczyna z Symfony. Niestety nie które kursy oparte są o SF2, więc trochę nie aktualne :D

Thanks Mihai...I appreciate it. I'm currently planning a Symfony API course..it will be paid but I'm gonna put some of the content on RU-vid such as API authentication for example

Sorry about that! Here's my docker-compose version: '3' services: database: image: postgres:13-alpine volumes: - ./postgres:/var/lib/postgresql/data restart: always environment: POSTGRES_USER: main POSTGRES_PASSWORD: secret POSTGRES_DB: security_app ports: [5432] mailer: image: schickling/mailcatcher ports: [1025, 1080]

Use a User repository to find the users you wish to display: www.doctrine-project.org/projects/doctrine-orm/en/2.9/reference/working-with-objects.html#by-simple-conditions Send the users to your view from your controller in a render method: symfony.com/doc/current/controller.html Then you can loop over your users and display the info about them in a twig template: {% for user in users %} {{ user.username }} {% endfor %}

You can add invalidate_session: true under the logout key in security.yaml

​@@GaryClarkeTech Thanks a lot Gary.

@@GaryClarkeTech Thanks but it's not working....

I'm afraid you've got no choice in that...that's how the core functionality was written, it's not something which you or me could change. The prefix is checked with each request and so having a fixed value makes sense I think.

Thanks for watching...I appreciate it. I never use anything that is no longer maintained and I don't think I've ever worked on a project that hasn't required maintenance. I'd always advise to follow best practices and stick with well maintained software.

I'll look at covering workflow at some point...I think I need to understand it a bit better myself first!

Think you must have missed a bit. It gets defined in the config.

If you're using mysql local to your machine, then remove the db entry from docker-compose

You're welcome Anton, cheers. Yes, you can have multiple firewalls but it's not recommended...I think even the docs recommend against this or maybe it's something I heard Ryan Weaver saying. Any disctinctions you need to make between customers and admins can be done with one firewall using roles and permissions. I'd say keep it simple.

​@@GaryClarkeTech Yeah I've already implemented that and then saw your response 😅 Is there any arguments against that? Because to me it seems very neat, can't find drawbacks in that setup.

Which package are you looking for? Try Packagist?

Thanks..you're welcome 👍

Auth has changed quite a lot since I recorded this. I'd check out Symfonycasts or the documentation itself.

@@GaryClarkeTech thanks a lot sir, will be waiting for an update, btw your tutorials are very detailed, thanks for the efforts

Welcome!

Thanks Mohamed 👍