[MGNLACTIVATION-57] Refactor private/public keys Created: 30/Mar/12 Updated: 15/Mar/21 Resolved: 15/Mar/21 |
|
| Status: | Closed |
| Project: | Activation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Jan Haderka | 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)
|
| Description |
|
Private/public keys introduced in 4.5 generate bit of confusion on setup for users. It would be beneficial to refactor storage and handling to be as close to ssh standards as possible (e.g. storing keys separately, rename property holding public key in repo to "authorized_key(s)" and so on). |
| Comments |
| Comment by Jan Haderka [ 15/Mar/21 ] |
|
Activation module have been superseded by publishing module. |