…kas)This PR was merged into the 3.4 branch.Discussion----------[Security/Http] fix parsing X509 emailAddress| Q             | A| ------------- | ---| Branch?       | 3.4| Bug fix?      | yes| New feature?  | no| Deprecations? | no| Tickets       |Fix#33636| License       | MIT| Doc PR        | -Commits-------fceb86b [Security/Http] fix parsing X509 emailAddress

…nticator (Spomky)This PR was squashed before being merged into the 6.3 branch.Discussion----------[Security] Allow custom user identifier for X509 authenticator| Q             | A| ------------- | ---| Branch?       | 6.3| Bug fix?      | no| New feature?  | yes| Deprecations? | no| Tickets       |Fix#47354| License       | MIT| Doc PR        | **to be created**This PR allows defining a custom user identifier instead of the hardcoded `emailAddress`.It also adds a new option for the firewall configuration:```yaml# config/packages/security.yamlsecurity:    # ...    firewalls:        main:            # ...            x509:                provider: your_user_provider                user_identifier: CN # default to emailAddress```**💬 Discussion**: user identifier regex changedNote that the regex is changed. The previous one was able to find an email address as expected, but now that the common name may not contain a `@` (or may contain more than one), it is required to update this part.It does not impact the previously merged PR#33759, but I prefer highlight the fact that it can now catch invalid email addresses set in `emailAddress`.Commits-------6479653 [Security] Allow custom user identifier for X509 authenticator