-
-
Notifications
You must be signed in to change notification settings - Fork 85
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
PHP ory/client:v0.2.0-alpha.60 and hydra 2.0.1, replayed client gets rejected due to serialization issues #224
Comments
Could you show the payload that gets sent by the client? :) That would be tremendously helpful! |
Hello, Here's the payload that gets sent:
(the important part is probably I've also dumped a repro here: https://github.com/AlbinoDrought/repro-ory-sdk-224 Cheers! |
Loosely related, but /**
* Create request for operation 'adminRevokeOAuth2ConsentSessions'
*
* @param string $subject The subject (Subject) whose consent sessions should be deleted. (required)
* @param string $client If set, deletes only those consent sessions by the Subject that have been granted to the specified OAuth 2.0 Client ID (optional)
* @param bool $all If set to `true` deletes all consent sessions by the Subject that have been granted. (optional)
*
* @throws \InvalidArgumentException
* @return \GuzzleHttp\Psr7\Request
*/
public function adminRevokeOAuth2ConsentSessionsRequest($subject, $client = null, $all = null)
{
// [ ...]
// query params
if ($all !== null) {
if('form' === 'form' && is_array($all)) {
foreach($all as $key => $value) {
$queryParams[$key] = $value;
}
}
else {
$queryParams['all'] = $all;
}
}
// [...]
}
Hydra explicitly checks for
Passing "true" would probably work but this gets rejected by static analysis tools:
|
Preflight checklist
Describe the bug
The PHP version of
ory/client:v0.2.0-alpha.60
sends invalidjwks
property in the below scenario:Reproducing the bug
Setup:
Reproduce:
Relevant log output
Relevant configuration
No response
Version
ory/client:v0.2.0-alpha.60, hydra 2.0.1
On which operating system are you observing this issue?
Linux
In which environment are you deploying?
Docker
Additional Context
Can be worked around with
$client->setJwks((object)[]);
or$client->setJwks(null);
The text was updated successfully, but these errors were encountered: