Hi again,
I think I got it figured out. We needed to rotate our activation keys a while back and because we are running magnolia in containers it was not possible to just generate the author keystore as they are mounted to the env from secrets etc. So I created new keys manually and updated the keystore to author and public keys to public instances but what I did not do was update the server/activation@publicKey on author instance to reflect the new key. I did not notice it because publishing works as author uses only the private key which was/is read from the keystore. Also magnolia password management is not used heavily as secrets are stored elsewhere.
Hope this helps if someone else stumbles into this. Also there could be a mention in the Activation Keys [1] documentation about the need to manually refresh the author public key if new keys are generated “manually” and not by using the “generate keys” functionality.
BR, Samuli
--
You received this message because you are subscribed to the Google Groups "Magnolia User Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to user-list+...@magnolia-cms.com.
To view this discussion on the web, visit https://groups.google.com/a/magnolia-cms.com/d/msgid/user-list/b890fab7-2bbe-4272-9001-d983bcba474an%40magnolia-cms.com.