... yes but to do that I have to know the existing keystore password, which without editing setup.py is going to be something random that is lost with the end of the python runtime. I can certainly change line 141 of setup.py from:
self.asimbaJksPass = None
to
self.asimbaJksPass = "MyAwesomePassword"
I was just wondering if editing that file was the desired pattern to control this... but I think I've answered my own question I'll submit a pull request to https://github.com/GluuFederation/community-edition-setup/blob/master/setup.py to allow this password to be spcified via the prompt when asimba is being installed.
Thanks!