Org2Org Provisioning: OAuth 2.0 Provisioning with Auto-key Rotation Failed due to "Verification failed: java.lang.RuntimeException: Cannot get DPoP nonce"

This issue pertains to the Okta Org2Org OIN app during OAuth 2.0, with Auto Key Rotation setup failing due to an error despite the customer performing all the documented steps as described in Okta documentation: Use OAuth 2.0 for provisioning (with automatic key rotation).

Verification failed: java.lang.RuntimeException: Cannot get DPoP nonce

• Org2Org Provisioning - OAuth with Auto key rotation
• Okta Integration Network (OIN)
• Failure to complete the OAuth with Auto key rotation setup due to Save error Verification failed: java.lang.RuntimeException: Cannot get DPoP nonce

Presuming everything is configured correctly as documented Use OAuth 2.0 for provisioning (with automatic key rotation), especially step 2(m.) Require Demonstrating Proof of Possession (DPoP) header in token requests checkbox, is configured as instructed, then the other possible root cause will be incorrect Base URL being configured under Org2Org > General tab. 

It is a common mistake for an Okta Admin to accidentally enter the Okta Admin Console URL (https://<subdomain>-admin.<okta|oktapreview>.com) instead of the Okta org URL (https://<subdomain>.<okta|oktapreview>.com) as the Base URL. 

To solve the issue, please follow the steps below:

1. Navigate to Okta Admin Console > Applications > Org2Org app > General tab. 
2. Locate the Base URL field, double-check the correct target Okta org URL is being configured as the base URL field value, in the following Okta org URL format: 
   1. https://<subdomain>.<okta|oktapreview>.com.
3. Save the correct Base URL field value. 
4. Navigate to Okta Admin Console > Applications > Org2Org app > Provisioning > Integration tab, click the Edit button, then reapply the Okta documentation steps: Use OAuth 2.0 for provisioning (with automatic key rotation) to configure/enable OAuth 2.0 with Auto key rotation provisioning method. 
5. Upon clicking the Save button, the verification should complete successfully without previous error.