Skip to content

CachedKeySet does not check HTTP response status code #499

Closed
@croensch

Description

@croensch

The CachedKeySet uses an PSR-18 HTTP client, sending a request and immediately decoding the answer - regardless of the response status code.

I tested a couple of failure scenarios around the connection but a working connection that produces an error is not checked. It leads to the UnexpectedValueException('"keys" member must exist in the JWK Set'). I propose a new UnexpectedValueException("HTTP ...").

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions