On macOS, Desktop Based Single Sign-On (DBSSO) fails to suppress Okta Verify FastPass because the service daemon fails to run. Run the Okta Verify installer over the existing installation to start the service daemon. When reviewing Okta Verify logs, the following error appears:

"DeviceSessionSignalSigner": {"message": "DBSSO FF is disabled from daemon MDM config", "defaultProperties": "", "location": "DeviceSessionSignalSigner.swift:isAvailable():}}

• Okta Identity Engine (OIE)
• Okta Classic Engine
• macOS
• Okta Verify
• Okta Device Access (ODA)
• Desktop Based Single Sign-On (DBSSO)

The service daemon fails to run on the machine. Administrators must install Okta Verify after pushing the configuration profiles to the machine. If the installation occurs before pushing the profiles, the service daemon fails to start.

How is the service daemon verified and started?

Verify the service daemon status using terminal commands, and run the Okta Verify installer over the existing installation to start the service daemon.

1. Run the following command in the terminal to verify the service daemon status:

   ps -ef | grep -i servicedaemon

2. Review the output for a "no such file or directory" message.
3. Ensure the property list file (plist) contains the service domain of com.okta.deviceaccess.servicedaemon and the OktaJoinEnabled key.

   <?xml version="1.0" encoding="UTF-8"?>  
   <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">  
   <plist version="1.0">  
   <dict>  
       <key>OktaJoinEnabled</key>  
       <true/>  
   </dict>  
   </plist>

4. Run the Okta Verify installer on top of the existing installation to start the service daemon if the files are missing.

Related References

• Desktop Based SSO for macOS