I finally got around to opening a ticket on this (actually what I believe to be a similar issue)
I had a client that was associated but couldn't get an IP address (was self assigning 169.254....). Support worked with me (and after prompting from my side)....we found the client in role
preauth_prof_0_2
ACL Name {preauth_prof_0_2 0} Number {165}
1: any any 17 0-65535 8209-8211 P4
2: any any 17 0-65535 4434-4434 P4
3: any any any 6 hits 756
4: any any any 4 hits 369
5: 0x888e 0xffff any any Pe4
6: any any any e4 hits 326
----------------------------------------------------------------
ACL Name {preauth_prof_0_2 1} Number {166}
1: any any 17 0-65535 8209-8211 P4
2: any any 17 0-65535 4434-4434 P4
3: any any any T6
4: any any any T4
5: 0x888e 0xffff any any Pe4
6: any any any e4
Unclear how to interpret the ACLs in the role.
This role assignment seems incorrect. The tech support engineer I worked with couldn't come up with anything except to disconnect the client, which got them into the right role.