The idea of Windows Hello PIN, is that that is local to your computer and not tied to the password... which means that you cannot use that to authenticate against ClearPass. Users should enter their AD account password for OnGuard, and while not tested in combination with Hello, you should be able to configure Windows SSO for OnGuard to overcome this issue.
If that doesn't work, please open a TAC case or have your local Aruba SE reach out to the product management team, as the request in itself sounds fair to me.
------------------------------
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.
------------------------------
Original Message:
Sent: Nov 17, 2021 08:49 AM
From: Alistair Wilkie
Subject: Windows Pin with Onguard
Hi,
Looking for some advice. Currently we have onguard set up to use windows credentials passthru but the new windows builds are using pin as part of windows hello. We are experiencing issues with failed authentications for windows machines due to this. Is there any way to authenticate onguard using the pin or any future updates that would help resolve this?
Thanks
------------------------------
Alistair Wilkie
------------------------------