You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 ...").