Maybe you can do som troubleshooting layer by layer.
Phase 1:
Is the SSID discovered and are the 802.11 frames do authenticate and associated succeed?
(HomeLAB-MC01) [MDC] *#show ap remote debug mgmt-frames ap-name HomeLAB-AP01 count 50
Phase 2:
Does L2 authentication WPA/WPA2/802.1x succeed? If the user is not in the station-table of the corresponding controller Phase2 is failing.
(HomeLAB-MC01) [MDC] *#show station-table
### Enable User-debugging ###
(HomeLAB-MM01) [##:##:##:##:##:##] (config) #logging user-debug 44:85:00:9b:48:80 subcat all level debugging
(HomeLAB-MM01) ^[##:##:##:##:##:##] (config) #write mem
(HomeLAB-MM01) ^[##:##:##:##:##:##] (config) #mdconnect
(HomeLAB-MC01) [MDC] *#show log user-debug 100
Phase 3:
Does the client get an IP address?
Phase 4:
What is the security policy that take place for the client?
Phase 5:
What network access doest the client get?
(HomeLAB-MM01) [##:##:##:##:##:##] (config) #logging network subcat dhcp level debugging
(HomeLAB-MM01) ^[##:##:##:##:##:##] (config) #write mem
(HomeLAB-MM01) ^[##:##:##:##:##:##] (config) #mdconnect
(HomeLAB-MC01) [MDC] *#show log network 50
Otherthings you can check.
What channels, channel-width,power-settings are used?
(HomeLAB-MC01) [MDC] *#show ap bss-table
"show user mac" give you a lot of information of a connected client.
(HomeLAB-MC01) [MDC] *#show user mac ##:##:##:##:##:##