Services Cannot be Started If Secure Admin Enabled and Non-Default Admin Credentials Used

[PeterParker]

Am I correct in saying that if secure admin has been enabled and non-default admin credentials have been used, then asadmin must be given a password file when calling (some/most/all of) its commands? One such example is creating a service, which includes a script to start the domain).

I have forked the repo and implemented a solution that works for my specific use-case, but I'm not sure what else this issue affects and therefore what else should be changed in the module. (E.g. it appears that PWFILE will never be populated).

Any thoughts you have would be appreciated.

[fatmcgav]

@PeterParker As it happens I've been hitting some issues with password files when running a cluster...

As far as I'm aware, asadmin will attempt to load from a standard location and the current password file gets put in that location.

However explicitly setting the password file might be a way around the issues I'm seeing...

Will try and have a play over the next few days and see what I can come up with...

[fatmcgav]

Also, it looks like I pass the passwordfile path to most of the defined types, such as create_cluster.pp

[PeterParker]

Yes -- I noticed that too. I suspect whenever asadmin is used and a custom credentials have been used then passwordfile should also be passed in -- but I'm far from a GlassFish expert.

[PeterParker]

Also, my proposed fix for my use-case probably breaks functionality for others since it passes in a passwordfile whether one has been specified or not.