[MGNLACTIVATION-124] Cannot Use Pre-Determined Keys Created: 11/Feb/16 Updated: 15/Mar/21 Resolved: 15/Mar/21 |
|
| Status: | Closed |
| Project: | Activation |
| Component/s: | None |
| Affects Version/s: | 5.4.2 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | OLD Chris Jennings (Malleus) (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| 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)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
I am attempting to configure multiple Magnolia environments that can communicate with each other via an extension of the activation framework. I am using magnolia.properties to point to a pre-prepared keypair file but the ActivationModuleVersionHandler overwrites the contents of this file. If a developer has prepared this file in advance, surely Magnolia should not attempt to rewrite it but should simply read in the contents? |
| Comments |
| Comment by Jan Haderka [ 15/Mar/21 ] |
|
Activation module have been superseded by publishing module. |