OS X Installer is EXTREMELY non-standard
There are two useful methods of installing software on OS X:
If the software is completely ( or near completely) contained within its package, then the dmg may contain the application or folder to be installed and an alias to /Applications This allows a drag and drop installation. During this process, if the user does not have permission to alter /Applications they will be asked to authenticate and given the opportunity to supply the username and password of a user who can alter /Applications This still allows the user to place the application wherever they would like.
The other way is to distribute the application as a pkg These files make use of /Applications/Utilities/Installer.app and place files in the specified location. During this process, if the user does not have permission to alter the specified location they will be asked to authenticate and given the opportunity to supply the username and password of a user who can alter location.
The custom installer used by SoapUI does not interact with the operating system in any meaning full way. When it encounters a permissions issue, it gives up instead of authenticating and performing the requested action as the authenticated user. Why is this important? Good security policy dictates that users do not use administrative accounts for general use. The methods described above include routine software installation in general use, the SoapUI installer does not. In short, installing SoapUI encourages insecure practices. If other software were to follow this same approach, the user would be encouraged to use an admin account all the time or install the software in ~/Applications (where it cannot be shared with other users)
.
If the software is completely ( or near completely) contained within its package, then the dmg may contain the application or folder to be installed and an alias to /Applications This allows a drag and drop installation. During this process, if the user does not have permission to alter /Applications they will be asked to authenticate and given the opportunity to supply the username and password of a user who can alter /Applications This still allows the user to place the application wherever they would like.
The other way is to distribute the application as a pkg These files make use of /Applications/Utilities/Installer.app and place files in the specified location. During this process, if the user does not have permission to alter the specified location they will be asked to authenticate and given the opportunity to supply the username and password of a user who can alter location.
The custom installer used by SoapUI does not interact with the operating system in any meaning full way. When it encounters a permissions issue, it gives up instead of authenticating and performing the requested action as the authenticated user. Why is this important? Good security policy dictates that users do not use administrative accounts for general use. The methods described above include routine software installation in general use, the SoapUI installer does not. In short, installing SoapUI encourages insecure practices. If other software were to follow this same approach, the user would be encouraged to use an admin account all the time or install the software in ~/Applications (where it cannot be shared with other users)
.