[MGNLXAA-56] When generating new activation key, Activation Tools - Key Management page still shows the old one Created: 04/Dec/12  Updated: 24/Jan/13  Resolved: 23/Jan/13

Status: Closed
Project: Transactional Activation
Component/s: None
Affects Version/s: 1.3.5
Fix Version/s: 1.3.6

Type: Bug Priority: Neutral
Reporter: Tomáš Gregovský Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
depends upon MAGNOLIA-4756 Allow to obtain public key, which was... Closed
depends upon MAGNOLIA-4791 SecurityUtil.updateKeys() results in ... Closed
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   

When you generating new key via tools > activation tools by clicking on "generate new key", then new key is generated, but text area on page show still old one, so if you copy it and put into public's, keys are different. If you reload a page (by clicking on activation tools in menu again) then field (textarea) show a new one.



 Comments   
Comment by Jan Haderka [ 21/Jan/13 ]
  • template changes should be reverted after applying changes from MAGNOLIA-4756 review
  • port to master is missing
Comment by Jan Haderka [ 22/Jan/13 ]
  79         SystemProperty.setProperty("magnolia.author.key.location", "target/key.store.properties");

This will work only as long as someone is using maven to build the module. You should have this file in src/test/resources so it can be found on a class path at runtime.

Comment by Roman Kovařík [ 23/Jan/13 ]

key.store.properties file should be deleted after the tests

Comment by Roman Kovařík [ 23/Jan/13 ]

fix test after MAGNOLIA-4791 will be solved

Generated at Mon Feb 12 11:06:38 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.