Can anyone explain to me how to improve the login status between ClearPass and Airwatch.
Clearpass are servers (4 25K) , Airwatch is a VM, All are internal to the network-- no proxy between servers.
We use airwatch to authenticate users with non-windows devices to the AD environment.
Do you have a HTTP proxy configured on the Clearpass appliances for Internet access?
If so, then the check to the Airwatch server is being sent to the proxy. If you are running version 6.5.2 there is now an option to bypass the proxy in the Airwatch context server set-up. If you are running a version below 6.5.2 this option is not present and you can get this error.
It is not whether there is a proxy between them, is the Clearpass configured for a proxy to access the Internet?
i have been having similar issues. so we noticed that we were getting errors in event viewer. we have Airwatch as an MDM mobile deployment which is in a SaaS enviroment. getting the following error attached.
clearpass Policy manager is on 184.108.40.206247
Error:401 means authentication/authorization failure. Ensure the credentials are correct between ClearPass and Airwatch.
You may also try increasing the account privilege/role to "System Administrator" in Airwatch and test, if the credentials are good.
Yeah is the first thing we tried to make sure the account had the right access but still we get this erros here and there....
I guet this every so often in one of my Airwatch servers (currently have 2 airwatch and 1 Jamf)
Issue/error goes away by re-typing the "api" password into your Airwatch box. For now that is the only way i resolve this problem.
At Aruba, we believe that the most dynamic customer experiences happen at the Edge. Our mission is to deliver innovative solutions that harness data at the Edge to drive powerful business outcomes.
© Copyright 2021 Hewlett Packard Enterprise Development LPAll Rights Reserved.