Skip to main content

My BOX and Salesforce connection was working fine, and the connection was established between the BOX and Salesforce until last week.

 

Starting this week, I am getting “Invalid Crypto Error” while Salesforce and BOX tries to connect.

No, update is being made on the Private Key, and the Private Key is not expired as well, and no updates are being made on the BOX as well. All of sudden, the connection between BOX and Salesforce died on me.

 

I tried to look for this issue in BOX and found this article which is not so helpful. My Private key is not encrypted to follow the encryption. I am using PKCS#8 PEM Format Private Key to connect it to BOX.

 

Any suggestion or help on this issue will be really appreciated.

Thank you!

👋 Hi ​@Nabina, welcome to the Box Community! Thank you for bringing this up.

 

We’ve identified that some users are experiencing an “Invalid Crypto Key” error when attempting to authenticate a client using the Salesforce SDK.


Our engineering team is actively working on a resolution. In the meantime, the suggested workaround is to use the Salesforce Developer Toolkit, if applicable.


If you need further assistance, please submit a ticket to our Product Support team.

 

Have a great day! 😊

Thank you for your feedback ​@Jey Bueno Box. The suggested workaround is not applicable to me, so I tried with the new private key and still getting the same “Invalid Crypto Key” error message. I am planning to open a case with Box, and hope that I will get the needed guidance and assistance.

 

Thank you!

Dear ​@Nabina, sorry to hear you're still encountering the same error.

 

I appreciate you submitting a support ticket. Please continue working with our Product Support team as they investigate the issue and provide further assistance.

 

Looking forward to getting this resolved for you! 🙌

We had escalated two cases w/ Box support over the last month when we first started seeing this error in a single client’s partial copy sandbox in code & config that had been unchanged since 2021 - A month of debugging, support cases, seeing this spread across all of our client’s (that are using Box) sandboxes, and finally a sev 2 escalation with Salesforce Partner Community support (who were very responsive & helpful once we escalated the case) led to a one-line code change from Salesforce support this weekend that has been deployed & verified in all of our clients, and has resolved the invalid crypto key error for us.

My GitHub comment here explains the line that changed, I’m still waiting for an answer as to why we needed to make this change, but it would appear the extra line-ending handling we had been doing since 2021 is no longer necessary: https://github.com/box/box-salesforce-sdk/issues/92#issuecomment-3225349426

Thank you very much ​@impactevolutionarcpa. Adding that line of code helped me resolve the “Invalid Crypto Key” error as well.

Thank you!

Reply


Terms & ConditionsCookie settings