Update "User authentication" customization example (4.6)

[adriendupuis]

Question	Answer
JIRA Ticket	IBX-11465
Versions	4.6
Edition	All

• "The password_hashers option was introduced in Symfony 5.3. In previous versions it was called encoders."
• Fix syntax errors
• Move code to code_samples/ files

TODO:

• check it really works on 4.6

Related RP: #3087

Checklist

• Text renders correctly
• Text has been checked with vale
• Description metadata is up to date
• Redirects cover removed/moved pages
• Code samples are working
• PHP code samples have been fixed with PHP CS fixer
• Added link to this PR in relevant JIRA ticket or code PR

[github-actions]

Preview of modified files

Preview of modified Markdown:

• docs/users/user_authentication.md

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[konradoboza]

Probably this config can be simplified with setting autowire: true and autoconfigure: true.

[adriendupuis]

The whole block might be removed as Subscribers are supposed to be automatically tagged as kernel.event_subscriber services…

[adriendupuis]

…confirmed, no need to declare this service, it's tagged and wired automatically.

[adriendupuis]

Removed in 9744cce

[github-actions]

code_samples/ change report

Before (on target branch)	After (in current PR)
code_samples/user_management/in_memory/config/packages/security.yaml	code_samples/user_management/in_memory/config/packages/security.yaml
	docs/users/user_authentication.md@40:``` yaml docs/users/user_authentication.md@41:[[= include_file('code_samples/user_management/in_memory/config/packages/security.yaml') =]] docs/users/user_authentication.md@42:``` 001⫶# config/packages/security.yaml 002⫶security: 003⫶ providers: 004⫶ # Chaining in_memory and ibexa user providers 005⫶ chain_provider: 006⫶ chain: 007⫶ providers: [in_memory, ibexa] 008⫶ ibexa: 009⫶ id: ibexa.security.user_provider 010⫶ in_memory: 011⫶ memory: 012⫶ users: 013⫶ # You will then be able to login with username "user" and password "userpass" 014⫶ user: { password: userpass, roles: [ 'ROLE_USER' ] } 015⫶ # The "in memory" provider requires an encoder for Symfony\Component\Security\Core\User\User 016⫶ password_hashers: 017⫶ Symfony\Component\Security\Core\User\User: plaintext
code_samples/user_management/in_memory/src/EventSubscriber/InteractiveLoginSubscriber.php	code_samples/user_management/in_memory/src/EventSubscriber/InteractiveLoginSubscriber.php
	docs/users/user_authentication.md@48:``` php docs/users/user_authentication.md@49:[[= include_file('code_samples/user_management/in_memory/src/EventSubscriber/InteractiveLoginSubscriber.php') =]] docs/users/user_authentication.md@50:``` 001⫶<?php declare(strict_types=1); 002⫶ 003⫶namespace App\EventSubscriber; 004⫶ 005⫶use Ibexa\Contracts\Core\Repository\UserService; 006⫶use Ibexa\Core\MVC\Symfony\Event\InteractiveLoginEvent; 007⫶use Ibexa\Core\MVC\Symfony\MVCEvents; 008⫶use Symfony\Component\EventDispatcher\EventSubscriberInterface; 009⫶ 010⫶final class InteractiveLoginSubscriber implements EventSubscriberInterface 011⫶{ 012⫶ private UserService $userService; 013⫶ 014⫶ public function __construct(UserService $userService) 015⫶ { 016⫶ $this->userService = $userService; 017⫶ } 018⫶ 019⫶ public static function getSubscribedEvents(): array 020⫶ { 021⫶ return [ 022⫶ MVCEvents::INTERACTIVE_LOGIN => 'onInteractiveLogin', 023⫶ ]; 024⫶ } 025⫶ 026⫶ public function onInteractiveLogin(InteractiveLoginEvent $event): void 027⫶ { 028⫶ // This loads a generic User and assigns it back to the event. 029⫶ // You may want to create Users here, or even load predefined Users depending on your own rules. 030⫶ $event->setApiUser($this->userService->loadUserByLogin('generic_user')); 031⫶ } 032⫶}

Download colorized diff