Magnolia 5.7 reached extended end of life on May 31, 2022. Support for this branch is limited, see End-of-life policy. Please note that to cover the extra maintenance effort, this EEoL period is a paid extension in the life of the branch. Customers who opt for the extended maintenance will need a new license key to run future versions of Magnolia 5.7. If you have any questions or to subscribe to the extended maintenance, please get in touch with your local contact at Magnolia.
Publishing or activation of content from author to public instances is authenticated using public-key cryptography. Public-key cryptography is a system that requires two separate keys: a public key to lock or encrypt the plain text request and a private key to unlock or decrypt the cyphertext request. Neither key can do both and neither is derivable from knowledge of the other. One is published and the other is kept private.
On receiving a publishing/activation request, a Magnolia public instance authenticates the author instance using a public key. The author instance generates the key automatically on first publishing/activation of content and transfers it to the public instance. You can generate new public keys any time on the author instance. A single public key is used for multiple public instances.
The authentication mechanism requires no configuration. The public key is generated automatically on the first activation of content and transferred to the public instance. The configuration of activation is stored in the
Configuration with the Publishing module in use:
Configuration with the Activation module in use:
The key pair is also stored on the local file system. If you use the default Magnolia bundle, the location is configured in a
Generating a new public key
You can create a new public key in the Publishing Tools app (shown in the screenshot below) or the older Activation Tools app, depending on which module you are using. Key lengths from 512 to 1024 bits are possible.
To generate a new public key:
- On the author instance, open the app in the TOOLS group:
- Click Generate new key. This generates a new public key and registers it automatically on the author instance.
- Copy the new key from the Current public key box.
- Sign into the public instances and open the Configuration app.
- Paste they key to Configuration >
Copy the newly generated public key to all public instances. It is not transferred automatically on activation as is the case with the initial key. You cannot activate the
publicKeynode to the public instance as at this point because a mismatch exists between the keys on author and public.