I have the same issue with Sonoma and JAMF Connect. This is what it has solved this issue for me.

Apple have significantly changed the macOS 14 login screen to match that of iOS (even now has a big digital clock in the middle of the screen etc.) in their march towards OS platform unity.  Jamf Connect is currently not compatible with this new login screen layout.  Disabling it when using the beta is currently the only option.  This also happened to me on an enrolled UTM virtual machine.

Jamf Connect 2.27 Beta 1 resolves this issue with Sonoma. PI112064.

I'm having this same issue. Hoping Jamf Connect 2.27 fixes it and that its released soon.

@gkempenich I am testing JAMF Connect Beta 2.27 and it resolves the issue with macOS Sonoma.

I'm also testing with the Jamf Connect beta for v2.27.0 and can confirm all is now working in our environment with macOS Sonoma once this version of Jamf Connect is used instead of earlier versions.

Jamf Connect v2.27.0 has now been released. Have carried out testing with this version of Jamf Connect on macOS Sonoma and can confirm the issues previously experienced are now resolved.

We cannot even boot devices into recovery mode.  It gives the "loading startup options" and then black screens there too.   I was running JC for months with Sonoma and hadn't had issues until RC2 was released.

we aren't able to boot into recovery mode.  I was running JC and didn't have issues until RC2 came out.  Anyone seeing this behavior?

I have a few "Happy" users who have updated to Sonoma before we could push out the update for JC to 2.27.0, but once I get to recovery mode. I cannot execute the "rm" commands, I keep on getting "no such file or directory" response from terminal.

These files dont seem to exist auth.db, auth.db-shm and auth.db.-wal

Any suggestions on why is happening?

Having the same issues after an accidental update from our end user. They only see a black display after signing in. Was able to regain access after running the below command.

/usr/local/bin/authchanger -reset -jamfconnect

/usr/local/bin/authchanger -reset -jamfconnect

I fixed my issue, I mounted the wrong drive....whoops!

can you share what you ran, we're having the same issue

I ran the exact commands listed above by @isradame's post.

The only difference is that when you go to Disk Utilty if you have Macintosh HD and Macintosh HD - DATA Volumes, you have to mount that DATA Volume as well, I had just mounted the regular one and that is why the commands were returning "No such file or directory" at the beginning.

Thanks

I'm using JAMFconnect 2.28 and I'm experiencing the same issue...

The original fix does work, but the key is mounting the correct volume. Here are the steps for the helpdesk:

-Boot into Recovery Mode
-Choose Options>Continue
-Select User, click Next, and enter password
-Go to Disk Utility>Continue
-Expand Macintosh HD volumes
-Click on Macintosh HD - Data
-Click on Mount in top-right corner and enter password

Macintosh HD - Data should now have the Unmount button in the top-right corner, indicating it's been mounted

-From top-left corner, Quit Disk Utility
-Go to Utilities>Terminal
-Type "cd /Volumes/Macintosh\\ HD/var/db/"
-Type one by one and press Enter:
rm ./auth.db
rm ./auth.db-shm
rm ./auth.db-wal

There should be no errors if commands ran successfully.

-Type "shutdown -r now" to reboot.
-Log in normally at first Mac login screen - the second login screen should now be gone.

If you run "/usr/local/bin/authchanger -reset -jamfconnect", which you should be doing anyway as a daily policy so everyone is authenticating via Jamf Connect, it will undo the settings and break it again. The permanent fix is to update Jamf Connect to v2.28. Confirm this version is installed on the Mac and you should be able to log in normally via Jamf Connect after a reboot. 

Thank you DREI. Unfortunately, it is not working on machine. Jamf Connect 2.28 and Sonoma 14.0 (23A344). It still show the black screen after I log out. I had to do the terminal:

Type "cd /Volumes/Macintosh\\ HD/var/db/"
-Type one by one and press Enter:
rm ./auth.db
rm ./auth.db-shm
rm ./auth.db-wal

-Type "shutdown -r now" to reboot.

as temporary to disable jamf connect.

You are confident the version is 2.28 on that endpoint? Both Jamf support and my environment have confirmed this fix. 

Yes, it is. I checked the jamf connect profile and it is 2.28. It doesn't work on MacOS Sonoma once I log out and it became black screen. (I am testing on one of the computer (test computer) before deploy to all computers.)

What do you mean by Jamf Connect profile? It's the application itself that needs to be 2.28. You should see this in Jamf under Inventory>Applicatinos>Jamf Connect.app for the test machine. 

same for me even if i'm using 2.28 Jamf Connect app....

Thank drei for pointing out about Jamf Connect. I am overlooking it since it is not assign to specific device once you review the version, please follow DREI's instruction and make sure Jamf Connect is 2.28 that assign that device then wait for few minutes before you log out and let it runs to update from old version to 2.28.

I can also confirm the recovery mode commands are not necessary if you are ready to deploy the latest version of Jamf Connect. Push out the policy to install Jamf Connect v2.28 with the launch agent, log into the affected Mac, and wait at the black screen 5-10 minutes. The first login screen decrypts File Vault, which has to happen before the Mac can connect to the Internet and receive policy updates. The other catch is doing this next to a known network since you can't see the screen to select a Wi-Fi network. Once the Mac is at the black screen (connected to power and automatically to its known Wi-Fi network), it will fix itself as soon as the new Jamf Connect is installed. You can verify the Mac is checking in and the status of the policy from Jamf Pro. 

Hey guys, we are having the same issue with a user's laptop who updated to macOS14 beta, and jamf connect broke. We tried this

cd /Volumes/Macintosh\\ HD/var/db/

rm ./auth.db

rm ./auth.db-shm

rm ./auth.db-wal

but those 3 files are not present on the laptop. The laptop had jamf running without issues until the macOS beta update, but has not reported back to jamf since the day the update was installed. We've been troubleshooting the laptop in recovery mode. 
Any ideas on how to proceed? Thanks!

/sbin/mount -uw /

macOS 10.15 or later. >>>.  mount -uw /System/Volumes/Data

Execute the following commands:

cd /var/db/

rm ./auth.db

rm ./auth.db-shm

rm ./auth.db-wal

Restart the computer by executing the following command

shutdown -r now