I'm trying to add an audience device into an existing capsman network. I have 3 CAP ACs all on 7.1.1 and this one audience. I do the usual setup and configure it to join 192.168.88.1 as capsman with certificate request on auto. And it fails misreably:
As soon as I stop capsman forcing requests the audience device joins correctly.

I was seeing such issues with a previous 7rc on the CAP ACs but I've reset capsman a few times and the audience is the only device that seems to have this limitation.

Another weird thing is the capnam seems invalid, I wonder if this is why it fails to create a cert as the name contains an invalid char? Any ideas?

I added some APs to my network and got the same error - CAP AC2 devices on ROS 7.2.1 and CAPsMAN on ROS 6.49.2. I do not know if this is related or if it will work, but maybe it does...

On my main RB controlling my APs I had to switch off the "Require Peer Certificate" setting and the request the cert on the AP, once the Cert then displayed in the AP config I could go back and re-enable this setting.

In my experience the sequence that you 1) enable CAP management, 2) request a new Cert and 3) lock it to the CAPsMAN was very unforgiving. Once you have the recipe down it always works.

Don't forget to make sure the date/time are set on the new AP. That was my issue, it wasn't trusting the root certificate because it was 1970