Hi, Can you please help me resolve the questions added above? We are totally blocked here

After debugging further at our end, we noticed that there was an issue with cert deployment which was causing this certificate mismatch. Even after this is fixed, license is not generated successfully. We are noticing an exception this time. Given the below contents of certificate.json file { "certificates" : [ { "certificate": "fps_certificate.bin", "1024-private-key": "priv_key_1024.pem", "2048-private-key": "priv_key_2048.pem", "provisioning-data": "provisioning_data.bin" } ] } we have below two queries the two private key files mentioned here should be encrypted with passphrase or it should be in clear without any encoding? Also when we generate csr, should we use encypted PEM or decrypted PEM. Please same paylods and apache error logs Sample payload - SampleJSONPayload.json SampleJSONPayload.json Apache error logs with encrypted PEM - Apache_Error_Log_encrypted_PEM.txt Apache_Error_Log_encrypted_PEM.txt Apache error logs with Decrypted PEM - Apache_Error_Log_Decrypted_PEM.txt Apache_Error_Log_Decrypted_PEM.txt If the answers to above queries are negative then we will have to raise a new csr.

we do understand that the test credentials provided along with SDK should not be used in production. Currently we have used test certificates shipped along with SDK to generate this SPC data. This is being done as part of POC to test the solution where request is generated in an internal test environment on a ipad.