The Windows client configuration determines how the client will authenticate to the network (User/Computer/User+Computer; as well the method PEAP [deprecated!!!!], EAP-TLS, TEAP). Then your Radius server (ClearPass in the documentation that you found, but as RADIUS and 802.1X are open standards, will than handle that authentication and return network access attribute, for Aruba typically an Aruba-User-Role and optional Aruba-User-VLAN.
If you can find how it should be configured with your Radius server (don't know it), it should work on any 802.1X compliant network, regardless the vendor. Only the role/VLAN assignment may be different. You probably can better ask your question in a forum for your NAC solution, as that is where in addition to the client most of the configuration should happen.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------