[magnolia-dev] [JIRA] (MGNLACTIVATION-108) magnolia-activation-keypair.properties behaviour during deploying

[JIRA (on behalf of David Caviedes Marquez)]

Title: Message Title

David Caviedes Marquez created an issue   Magnolia Activation Module / MGNLACTIVATION-108 magnolia-activation-keypair.properties behaviour during deploying Issue Type: Bug Affects Versions: 5.3.1 Assignee: Unassigned Created: 30/Apr/15 6:33 PM Environment: O.S Ubuntu 64 bits 14.04.02 LTS // Magnolia CMS 5.3.6 // Java 1.7.0_76 Labels: keypair properties activation handshake Priority: Blocker Reporter: David Caviedes Marquez We have found some problems when deploying magnolia WAR application in both author and public instances: Once both instances are deployed, we try to publish some content from Author to Public and an error appears saying "Handshake information for activation was incorrect. Someone attempted to impersonate author instance. Incoming request was from ..." We solve this problem following these insttructions: https://documentation.magnolia-cms.com/display/DOCS45/Activation+security#Activationsecurity-Generatinganewpublickey But this is a manual solution, so we need an "automatic" solution. Lookin for the origin of the problem, we found this: http://forums.magnolia-cms.com/forum/thread.html?threadId=c648e05d-40a4-4f8a-81c7-a5631900807a#ad9165a9-36b9-4178-b4e2-0521b901cedd So we noticed that during deploying process we overwrite magnolia-activation-keypair.properties file with and old version (with an old key) of it. Then we open magnolia.properties file and see that related to it: "# Location of the file containing both the private and the public keys used to verify authenticity of activation requests This file is generated if not present" The fact is that if we delete "magnolia-activation-keypair.properties" and restart the instance, the file isn´t generated automatically so, when is this file generated if not exists? Moreover we noticed that in public instances this file is not necessary because if we delete it we can publish content without problem (if the correct "magnolia-activation-keypair.properties" is present in author instance). Is that correct? We think two possible solutions: 1.- Include the correct "magnolia-activation-keypair.properties" in the WAR deployed 2.- Change (in magnolia.properties file) the directory of "magnolia-activation-keypair.properties" and make it to point to an external directory, so we won´t overwrite this file when deploying the WAR Are these correct solutions? What is the real behaviour of Magnolia with activation process and "magnolia-activation-keypair.properties" file? Thanks in advance Add Comment   This message was sent by Atlassian JIRA (v6.4.1#64016-sha1:5d75814) ---------------------------------------------------------------- For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------