I just got a new Pi Zero 2 W and it will not connect to MikroTik if I'm using a secure connection. If I have an open unsecure connection it connects just fine. I’ve tested Raspberry Pi OS Lite (Bullseye and Bookworm, 32-bit and 64-bit), with the latest version on Bookworm including firmware 7.45.96.s1.
I've also tested on a few different versions of Ubuntu, nothing will connect. On the Mikrotik side, I've tested with both AX devices and AC devices to rule out any issues with AX. On the AC devices I have test both v6 and v7.
The Pi Zero 2 W consistently fails to connect to secure WPA2-PSK networks on my Mikrotik routers, despite correct credentials. It connects successfully to unsecured networks with no issues. I also tested with a phone hotspot with WPA2-PSK security and it connected to it with no issues.

Mikrotik logs show association timeouts or authentication failures

This is limited to the Pi Zero 2 W, other Pi such as the Pi 4 with the CYW43455 chip connect just fine.

I found a post, I think was on reddit, describing the same issue, specifically using the Pi Zero 2 W.. That person tried using multiple Zero 2 Ws, all new, none would connect, when swapping SD cards into other Pis they would connect without issue.

It appears this is specific to the chip used in the zero 2 w (CYW43439) and MikroTik.
Are there any known firmware versions for MikroTik specifically addressing this particular chip?

If you dont have a log entry and you have FT enabled.

Try disabling it.
FT sometimes causes issues with devices that don't support it.

FT??

FT??

802.11r

If you dont have a log entry and you have FT enabled.

Try disabling it.
FT sometimes causes issues with devices that don't support it.

I'm pretty sure I didn't have FT enabled, I'm not even sure what FT is and haven't used it unless it's enabled by default. Nothing really in logs other than maybe some time out messages.. For the time being I had to move on to get it working so I made a hidden network and restricted it by MAC as a work around. I would be curious to see if anyone else is able to get this working..

I feel your pain man, I had been living with issue for about a year. I tried all possible combinations of shenanigans, that I got a headache. Eventually it appeared to be a bug in the Broadcom driver for Raspberry PI. And the fix is relatively simple: just add this magic to the end of the file.
This solution was described here