[MGNLACTIVATION-171] Module should check if the keypair file exists before it creates it during the installation phase Created: 21/Sep/17 Updated: 15/Mar/21 Resolved: 15/Mar/21 |
|
| Status: | Closed |
| Project: | Activation |
| Component/s: | None |
| Affects Version/s: | 5.5.5 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Ondrej Chytil | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | quickwin | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Date of First Response: |
| 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:
ActivationModuleVersionHandler should perform a check for the existence of this file before it generates a new one. |
| Comments |
| Comment by Jan Haderka [ 15/Mar/21 ] |
|
Activation module have been superseded by publishing module. |