test: dpop

[salvatorelaiso]

While testing the property is_valid of DPoPVerifier, I found out it can fail on some invalid inputs.
Specifically, you can find some commented out test cases which causes the aforementioned property to raise different errors on not-valid inputs. Do you prefer to address those cases, for example, by returning False if any of the underlying checks raise an error, or we keep it as it is?

[peppelinux]

is_valid MUST return a boolean

please specify it if not already defined in the property/function definition

in the test we have to assert true or false, depending by the scope of the test

[peppelinux]

we must tests situation where the dpop is invalid or with a wrong schema, the tests we need wants to cover also the security aspects and not just the assertion to wellknown parameter, that we have used in the tests

[salvatorelaiso]

As you can see, the test cases for the DPoPVerifier are cases in which we expect the function to return False but instead it raises an error. Do you want this behavior to be fixed in the function? The tests failing are exactly addressing cases in which the parameters are not correct, we can also expand those tests with new cases.