some mtls aliased endpoints use is not enforced in fapi2 client tests

What did you do?

A request to non-mtls-aliased PAR endpoint failed, I have fixed the client configuration to use the aliases and the PAR call succeeded, but surprisingly, the same requirement to use the aliased endpoints did not come up for the token endpoint interaction.

What did you expect would happen?

I would expect the tests to fail when mtls client auth with dpop sender constraining is used and the client doesn't use the mtls aliased token endpoint.

What did happen?

Tests passed despite not using the aliased token endpoint

https://www.certification.openid.net/log-detail.html?log=MMbftNJmJZY1Sc8