-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[Security] OIDC user info token handler client #18354
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Security] OIDC user info token handler client #18354
Conversation
…ler client (vincentchalamon) This PR was squashed before being merged into the 6.3 branch. Discussion ---------- [SecurityBundle] Fix configuring OIDC user info token handler client | Q | A | ------------- | --- | Branch? | 6.3 | Bug fix? | no | New feature? | no | Deprecations? | no | Tickets | N/A | License | MIT | Doc PR | symfony/symfony-docs#18354 Cf. #50453 (comment) Commits ------- 23c9e17 [SecurityBundle] Fix configuring OIDC user info token handler client
@nicolas-grekas are you aware of this issue? |
Needs a fix indeed... |
OK found it: ->set('security.access_token_handler.oidc.signature', Algorithm::class)
->abstract()
->factory([SignatureAlgorithmFactory::class, 'create'])
->args([
abstract_arg('signature algorithm'),
])
->set('security.access_token_handler.oidc.signature.ES256', ES256::class)
->parent('security.access_token_handler.oidc.signature')
->args(['index_0' => 'ES256']) @nicolas-grekas is there any way to declare an abstract factory, or should I call the factory on each service declaration? |
Strange, I would expect this to work. I can have a look a bit later. |
Thank you Vincent. |
No description provided.