A client is having an issue onboarding the Box connector because we’re getting an error extracting the private key:
We have tried entering the private key in multiple formats (escaped/unescaped, with “-----BEGIN ENCRYPTED PRIVATE KEY-----” and end, without, etc) but we keep getting this error. The credentials were provided by the Box team in JSON format:
Anyone have any pointers?
Thank you!
I ran into a similar issue with the SuccessFactors connector and thought this might help. When working with certificates, especially for connectors, it’s crucial to extract the certificate directly from the source—like Box—and insert it exactly as is. Be cautious with private keys; editing them manually in your own text or PEM files can introduce hidden characters that corrupt the key.
I recommend opening the certificate in a lightweight text editor like Notepad, Notepad++, or VS Code, and avoid making any changes to the content. This approach resolved my issue, so it might be worth trying here too.
Thanks for the reply. The screenshot is from the JSON file that the Box team generated when sharing the key. We’ve tried copying it exactly as is from the file, but still no luck.
Are you able to validate connectivity via other means? Perhaps a CURL call and/or a call via Postman or a python script?
I’ll have to ask the client Box team to try that
