Access allowed despite authentication failure

Testing version: 5.6.4
Having got an access token using DPoP, if I make a request to a resource but use the token in Bearer mode instead of signing the request with DPoP again, the request succeeds whilst also reporting access denied.

www-authenticate: [Bearer realm="https://inrupt.net", error="access_denied", error_description="Token does not pass the audience allow filter"]

Similarly, if I create a bad DPoP token using the wrong htm I still get the resource despite:

www-authenticate: [Bearer realm="https://inrupt.net", error="invalid_token", error_description="Invalid PoP token"]

Lastly, creating an invalid DPoP token with a different htu gives me:

www-authenticate: [Bearer realm="https://inrupt.net", error="invalid_token", error_description="htu https://solid-test-suite-alice.inrupt.net/private/asdasd does not match https://solid-test-suite-alice.inrupt.net/private/"]

whilst also succeeding with the request.

I was just about to post this when I thought of other tests I could do. I sent an invalid Bearer token and it still worked:

www-authenticate: [Bearer realm="https://inrupt.net", error="invalid_token", error_description="Access token is not a JWT"]

It seems that having an active session overrides all other security considerations as all the above fail when there is no session.

Es werden keine Dateien, Tests oder Einstiegspunkte genannt. Reproduziere die gemeldeten Fälle mit Version 5.6.4 und einer aktiven Sitzung: die Verwendung eines DPoP-Tokens als Bearer, ungültige htm- und htu-Werte sowie ein ungültiges Bearer-Token. Als erledigt gilt die Aufgabe, wenn jeder Authentifizierungsfehler den Zugriff auf die Ressource verweigert, anstatt die Anfrage zuzulassen.