Uploaded image for project: 'Activation'
  1. Activation
  2. MGNLACTIVATION-171

Module should check if the keypair file exists before it creates it during the installation phase

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Won't Fix
    • Neutral
    • None
    • 5.5.5

    Description

      When the activation modules is installed it generates and stores the private and public keys and stores them under location defined by the magnolia.author.key.location property. If some file already exists on the given location it gets overwritten despite the comment in the bundled magnolia.properties file:

      This file is generated if not present

      ActivationModuleVersionHandler should perform a check for the existence of this file before it generates a new one.

      Checklists

        Acceptance criteria

        Attachments

          Activity

            People

              Unassigned Unassigned
              ochytil Ondrej Chytil
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Checklists

                  Task DoD