CMAM-172237: In AirWatch 8.2, a VPP sToken sync will fail if the AirWatch Console is leveraging a proxy for outbound communication

Symptoms

In AirWatch 8.2, a VPP sToken sync from the AirWatch Console will fail if outbound communication for the Console is configured to go through a proxy.  The sync will function correctly if no outbound proxy is configured in the Console.  

Workaround

The following changes can be manually implemented in the AW.integrationService.config file to properly support the outbound proxy configuration.  The service must be restarted after the changes are implemented.  We strongly recommend taking a backup of the config file before making any changes.

Add the following line to the end of the <add key> declarations:

<add key="ProxySettings" value="ConsoleProxy" />

 

Add the following section after the <appsettings>...</appsettings> section:

<system.net> 
<defaultProxy enabled="true" useDefaultCredentials="false">
<module type="WanderingWiFi.AirWatch.ProviderFactory.Utility.AWProxy, WanderingWiFi.AirWatch.ProviderFactory, Version=6.0.0.0, Culture=neutral">
</module>
</defaultProxy>
</system.net>

Resolutions

This issue has been given identifier CMAM-172237.  Our product team has been engaged and is working on a resolution with an update to the AirWatch Console.

Have more questions? Submit a request

0 Comments

Article is closed for comments.