DCP-o-matic

I have a strange case of clairmeta validation showing as failed but the DCP still loads and plays well in DOM player.

I will check this DCP in the cinemas tomorrow but was wondering if someone could please shed some light on this. The error log is as below.

2022-08-17 03:41:03,983 - Clairmeta - INFO - Error(s) :
check_certif_fields_encoding - pkl_ea14b3ac-3088-49ea-bf3e-90aa8812c494.xml (Certificate : 5) : Issuer organizationName field encoding should be PrintableString, got UTF8String
check_certif_fields_encoding - pkl_ea14b3ac-3088-49ea-bf3e-90aa8812c494.xml (Certificate : 6) : Issuer organizationName field encoding should be PrintableString, got UTF8String
check_certif_fields_encoding - pkl_ea14b3ac-3088-49ea-bf3e-90aa8812c494.xml (Certificate : 7) : Issuer organizationName field encoding should be PrintableString, got UTF8String
check_certif_fields_encoding - cpl_bac36f5c-8610-4a8e-a6e1-ba83d84e1aaa.xml (Certificate : 5) : Issuer organizationName field encoding should be PrintableString, got UTF8String
check_certif_fields_encoding - cpl_bac36f5c-8610-4a8e-a6e1-ba83d84e1aaa.xml (Certificate : 6) : Issuer organizationName field encoding should be PrintableString, got UTF8String
check_certif_fields_encoding - cpl_bac36f5c-8610-4a8e-a6e1-ba83d84e1aaa.xml (Certificate : 7) : Issuer organizationName field encoding should be PrintableString, got UTF8String
2022-08-17 03:41:03,984 - Clairmeta - INFO - Total check : 76
2022-08-17 03:41:03,984 - Clairmeta - INFO - Total time : 3.11 sec
2022-08-17 03:41:03,986 - Clairmeta - INFO - Validation : Fail

It's an error that was made when creating the certificates used to sign the DCP - there was a bug in DoM until a few years ago that made (incorrect) certificates in this way. Nowadays DCP-o-matic should spot if you have certs like that and offer to fix them for you. Did DCP-o-matic make the DCP?

Thanks Carl. Yes. The DCP was made using DCP-o-Matic.

Is it ok to hand over this DCP to the cinemas given this validation error or shall I look at corrections it first?

I think I am using the old version but my fear is that if I upgrade to the newer version then I might lose the existing certificas which I am using for KDM Generation also. This has kept me away from the update. Is there a way to make the old certificate work and still be able to update and continue using the KDM Creator tool with my existing DKDMs?

This issue does not impact encryption certificates. Just play safe and backup your config before you upgrade and recreate the new signing certs.

Dear Carl, Will the old DKDMs still work for generating new KDMs if I generate new signing certificates?

I think they should do, but as Carsten says - be safe and back up your configuration before you try it!