File based keystores and the KeyStore store() method
The update model for file based keystores is a replace model. When the application uses the store() method for a file based keystore, the contents of the KeyStore object in the application memory replace the current persistent data for the keystore. In other words, any KeyStore update that has been successful will be reflected in the new version of the persistent data for the keystore.
One consequence of the replace model occurs if two applications
are updating the same keystore at the same time. To illustrate, suppose
application app1 and application app2 are modifying some keystore
and
- app1 loads the keystore into a KeyStore object and makes some updates
- app2 loads the keystore into a KeyStore object and makes some updates
- app1 stores the contents of the KeyStore object into the persistent keystore data
- app2 stores the contents of the KeyStore object into the persistent keystore data
In this case, because the app1 changes were not stored in persistent data before app2 loaded the keystore, and because app2 replaced the persistent data after app1, updates made by app1 are overwritten by app2.