The publisher ID is derived from the signing certificate distinguished name, but also incorporates the distinguished names of the other certs in the chain. So, yes, this is the expected behavior.
Thanks for holding this discussion.
I need your help with regards to signing, certificates renewal and publisher id.
Our team is working on a serious AIR app out there, having a considerable install base. We've now renewed our certificate for the second time, but this time the compiler would generate a different publisher ID. How could that possibly happen, anyone any idea?
Please note, that we've already done that before, we're completely aware that publisher id is generated based on details in the certificate. We also had to renew the previous certificate a couple of times, because different details was causing a different publisher ID. It is totally confirmed that all the details in the current certificate are exactly the same, all of them. But still, the publisher ID is different and that is a nightmare. I'll can share other more complicated explorations further on in the discussion, but this is the first question that needs to be answered.
I'm also posting this is another relevant thread: