The DPoP proof JWT cannot be parsed

[nyklav]

Describe the bug?

I have an API Services application configured to use a Public Key / Private Key.

According to the documentation, DPoP should have been handled automatically, but it threw the error.

Error calling GetBearerToken:

{
  "error": "invalid_dpop_proof",
  "error_description": "DPoP proof JWT cannot be parsed."
}

What is expected to happen?

DPoP should be handled automatically.

What is the actual behavior?

The error “DPoP proof JWT cannot be parsed” occurs.

Reproduction Steps?

Try to get an access token using a Private Key with the “Require Demonstrating Proof of Possession (DPoP)” option enabled

Additional Information?

No response

.NET Version

8.0.403

SDK Version

9.0.0

OS version

BuildNumber	Caption	OSArchitecture	Version
19045	Microsoft Windows	10 Pro 64-bit	10.0.19045

[bryanapellanes-okta]

@nyklav Thanks for bringing this to our attention and I apologize for the delayed response. I've entered an internal issue for tracking and prioritization: OKTA-832982