CDP SDK Private Key Authentication Failure - Unable to Initialize Agent - Critical Issue Blocking Development

[arhansuba]

I am encountering persistent authentication failures with the CDP SDK across both the official example code and custom implementations. Despite extensive troubleshooting and following all documentation guidelines, the SDK consistently fails to authenticate with the provided API credentials.

Example Project: CDP Agentkit Chatbot Example

Implementation Attempts:

Official CDP Example Project:

Followed the exact implementation from the CDP documentation
Used the provided example code without modifications
Encountered the same authentication error
Attempted multiple private key formatting approaches

Custom Project Implementation:

Developed according to CDP SDK documentation
Implemented all recommended security practices
Encountered identical authentication failures
Hours of troubleshooting yielded no resolution

Error Message:
'Could not deserialize key data. The data may be in an incorrect format, the provided password may be incorrect, it may be encrypted with an unsupported algorithm, or it may be an unsupported key type (e.g. EC curves with explicit parameters).', [<OpenSSLError(code=503841036, lib=60, reason=524556, reason_text=unsupported)>]
Troubleshooting Steps Taken:

Verified API credentials multiple times in CDP Portal
Attempted various private key formatting approaches
Tested different environment variable configurations
Tried multiple fresh installations
Reviewed all available documentation thoroughly
Spent several days attempting different solutions

Critical Impact:

Complete blockage of development progress
Unable to proceed with any CDP SDK functionality
Both example and custom implementations are non-functional
Significant time lost to troubleshooting

Expected Behavior:
The SDK should successfully authenticate using the provided API credentials and initialize the CDP Agentkit wrapper, allowing development to proceed.
Urgent Resolution Needed:
Given that this issue persists across both official examples and custom implementations, and prevents any development progress, urgent guidance or resolution would be greatly appreciated.