Hello, I've observed that the OpenID4VCIClient consistently utilizes the nonce from the access token acquisition response. However, there's a scenario where we need to make multiple sequential calls to the server to retrieve credentials using the same access token. In this case, each request requires a nonce from the preceding server response. Presently, the implementation relies on the same nonce for each request, resulting in the failure of subsequent requests due to nonce invalidity.
Hello, I've observed that the OpenID4VCIClient consistently utilizes the nonce from the access token acquisition response. However, there's a scenario where we need to make multiple sequential calls to the server to retrieve credentials using the same access token. In this case, each request requires a nonce from the preceding server response. Presently, the implementation relies on the same nonce for each request, resulting in the failure of subsequent requests due to nonce invalidity.