[SOLVED] CB and Akeeba Admin Tools

I am posting this here and @Akeeba.
It seems like Akeeba isn´t CB aware???

When I promote a user from Administrator to Super User, using CB User manager, Admin Tools blocks the user and this email is sent to me:

It doesn´t help to unblock the user in Joomla user manager, the user gets blocked again immediately after login attempt.

Nothing we can do about it. It's a feature of Akeeba Admin Tools detecting what component performed the usergroup change and in this case it's com_comprofiler (CB) and not com_users (Joomla). They'd have to implement support for CB in that check. I imagine the same will happen with any extension modifying a user object and adding/removing the super users usergroup.

krileon wrote: Nothing we can do about it. It's a feature of Akeeba Admin Tools detecting what component performed the usergroup change and in this case it's com_comprofiler (CB) and not com_users (Joomla). They'd have to implement support for CB in that check. I imagine the same will happen with any extension modifying a user object and adding/removing the super users usergroup.

Agree. Only thing you could do in such case is make them aware...

I got an answer from them that solves the problem (I´m not saying it is the best solution)
but I´m posting it here for the benefit of other CB users:

Admin Tools is aware that third party software created a Super User on your site. In most cases, that's a bad thing. In this particular case, you know what's doing it and you want it to be allowed to do it.

Go to Web Application Firewall, Configure WAF, on the Joomla! Feature Hardening Options tab, and set Disable creating / editing backend users from the frontend to No. That will allow Community Builder to create the Super User.

Go to Web Application Firewall, Configure WAF, on the Joomla! Feature Hardening Options tab, and set Disable creating / editing backend users from the frontend to No. That will allow Community Builder to create the Super User.

Says that feature is for frontend though yet it affected backend and was checking what component made the change instead of just checking the Joomla client id to determine if was from frontend or backend. Seams like something maybe wrong with that check behavior or the wording of the parameter, but regardless thank you for sharing your findings.

This little "feature" is causing lots of issues for users and support tickets for them.
It looks like it will be removed from next version of AT.

Issue solved.