[AAA-124] Encryption Service config should have randomly generated key and salt Created: 26/Apr/17 Updated: 21/Mar/19 |
|
| Status: | Confirmed |
| Project: | aaa |
| Component/s: | General |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | ||
| Reporter: | Ryan Goulding | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Description |
|
Due to the fact that updating the config for encryption key/salt dynamically causes a blueprint container restart (clustered-app-config), we need to find a better way to inject these properties upon first start (bootstrap). For now, it is left to the operator to fill in his/her unique byte encoded values. |
| Comments |
| Comment by Ryan Goulding [ 26/Apr/17 ] |
|
See |