SAS configuration is lost after reboot or stopping SMF services on Solaris 11 after upgrading to SAS 7.0 (4383074)

After upgrading to Safeguard Authentication Services (SAS) 7.0 on Solaris 11, the following behavior may be observed:

• SAS upgrade completes successfully and services start normally
• After a system reboot, SAS configuration is no longer present
• SAS configuration is lost after stopping either of the following SMF services:
  • svc:/site/vasgp-config:default
  • svc:/site/vasclnt-config:default
• No warnings or errors are logged at the time the configuration is lost
• Restarting vasd does not restore the configuration

On Solaris 11, IPS packaging wraps SVR4 post-install and pre-removal scripts as transient SMF configuration services. In SAS 7.0, these configuration-related SMF services are started as part of the installation and configuration handling process.

Disabling these SMF configuration services may trigger pre-removal logic, resulting in SAS being left unconfigured. This behavior is not expected to occur outside of an actual package removal operation, but has been identified under certain conditions in SAS 7.0.

This issue has been confirmed as a product defect.

This issue is being tracked internally as bug ID 704862. A corrective update is planned for a future SAS release; however, a specific release date has not been confirmed.

As a mitigation, customers running Solaris 11 may install SAS using the SVR4 installation variant, which avoids the affected IPS packaging behavior.

Workaround example:

./install.sh --variant svr4