AutoUpgrade stores your MOS credentials and other secrets in its own keystore.

It’s convenient to create an auto-login keystore. Otherwise, AutoUpgrade prompts for the keystore password every time it needs a secret. But the auto-login keystore only works on the computer where it was created.

Unless you create a shared keystore. Let’s see how.

Shared Keystore

1. If you have an existing AutoUpgrade auto-login keystore, remove it:

   rm /home/oracle/autoupgrade-patching/keystore/cwallet.sso*
   

   • Only remove the auto-login keystore files.
   • They are prefixed cwallet.sso.
   • The keystore location is defined by the config file entry global.keystore.
2. Start the AutoUpgrade password console:

   java -jar autoupgrade.jar -config get-patches.cfg -patch -load_password
   

3. AutoUpgrade prompts for the keystore password:

   Processing config file ...
   Loading AutoUpgrade Patching keystore
   Enter wallet password:
   

4. Create a shared keystore using the save command:

   MOS> save
   Select auto-login mode for the AutoUpgrade Patching keystore [YES|NO|SHARED]: SHARED
   

   • Enter SHARED when prompted for the auto-login keystore mode.
5. Exit the password console:

   MOS> exit
   

6. You can now use the auto-login keystore on other computers.

Security

A shared keystore is a secure way to store your credentials, although it is not as secure as a regular keystore.

Be sure to protect your keystores, shared or not, by having restrictive file permissions and perhaps even file system auditing.

That’s It

Automation is key these days, and this enhancement makes AutoUpgrade fit better with that ambition.

If there’s anything we can do to make AutoUpgrade even better for automation, drop a comment below.

Happy patching!