Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR:
The bug has been discovered by my colleage @ileanatudoran, props to her!
How to reproduce the issue?
When you want to introspect the access token using
client_secret_jwt
, theIntrospectionService
seems to be your friend.Inside
IntrospectionService::introspect()
, theClientSecretJwt AuthMethodInterface
callsAbstractJwtAuth::createRequest()
and do:
Then, that
$request
object is returned back inIntrospectionService::introspect()
and the body of the$request
is modified:The issue is when we do:
By using the
write()
method, it will append the generated query string to the$request
body.So, you could end up having a request body as such:
client_assertion=tokenvalue&client_id=value1&client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearertoken=token
There is a missing
&
betweem the original request bodyclient_assertion=tokenvalue&client_id=value1&client_assertion_type=urn:ietf:params:oauth:client-assertion-type:jwt-bearer
andtoken=token
.