-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Won't Fix
-
Affects Version/s: 6.0.0, 6.5.2.2
-
Fix Version/s: None
-
Component/s: secrets
-
Labels:
-
Rank:1|hzzyrj:
-
Sprint:AM Sustaining Sprint 72, AM Sustaining Sprint 73
-
Story Points:5
-
Support Ticket IDs:
-
Needs QA verification:No
-
Functional tests:No
-
Are the reproduction steps defined?:Yes and I used the same an in the description, Yes but I used my own steps. (If so, please add them in a new comment)
Bug description
When copying the original keystore.jceks to a different location and update AM to use this as its feaure keystore, that modifies the bootstrap file (boot.json). There seems to be a special link to the original keystore file; when using a completely new keystore, it doesn't modify the boot.json.
How to reproduce the issue
- Install vanilla AM
- copy keystore.jceks .storepass & .keypass to a different location
- Update the AM Server defaults > Security > KeyStore with the new files' location
- Restart AM
- Check the boot.json - it now points to the new keystore file.
Expected behaviour
Bootstrap keystore is irrelavant to the keystore used for AM features and any changes there shouldn't affect the boot.json file.
Current behaviour
Boot.json is modified by AM pointing to the new keystore
Work around
Create a new Keystore from scratch instead of copying the default one.
- is duplicated by
-
OPENAM-14991 Changes to boot.json are overwritten
-
- Resolved
-
- is related to
-
OPENAM-16078 Documentation changes to help avoid additional tickets relating to AM boot.json usage and updates
-
- Resolved
-
- relates to
-
OPENAM-14991 Changes to boot.json are overwritten
-
- Resolved
-
-
OPENAM-14371 Document suggestions for AM 6.5 Configuring Keystores
-
- Resolved
-