Post Auth tab takes almost 2 minutes to Save

Version Affected:  All

Description:  
This specifically applies to Air-Gapped deployments but can also apply to non Air-Gapped deployments if internet access is limited

Saving the Post Auth page can take a very long time, sometimes close to 120 seconds
The delay is seen against the 'WebAdminComplete.aspx' page




Cause:  
Amongst other causes, this has been seen to be caused by dotnet attempting to reach out to Microsoft for various reasons, this can be seen in a Wireshark or NetMon Trace carried out during a Save of the Post Auth tab

Resolution:  
Add an OUTGOING Firewall Rule to BLOCK the dotnet.exe process for all but internal IP Addresses
If details around how to create this specific rule are needed, please see the following article - https://support.secureauth.com/hc/en-us/articles/35616608548500

For other possible causes of the delay when saving the Post Auth page in Air-Gapped deployments see the following article - https://support.secureauth.com/hc/en-us/articles/35616302814356

Special Considerations (optional as needed):  
Creating Firewall Rules can cause communication problems in unexpected ways, ensure the correct steps are followed to avoid unexpected results

SecureAuth Knowledge Base Articles provide information based on specific use cases and may not apply to all appliances or configurations. Be advised that these instructions could cause harm to the environment if not followed correctly or if they do not apply to the current use case.

Customers are responsible for their own due diligence prior to utilizing this information and agree that SecureAuth is not liable for any issues caused by misconfiguration directly or indirectly related to SecureAuth products.