Webgateway 9.2.3 block Autodesk licensing

[alpha-soft]

Hello,

for us, the web gateway blocks cleaner communication of Autodesk products (Inventor, Desktop APP, etc.). Apparently, authentication with the proxy cannot be passed cleanly. Does someone have a rule set that can be used to exclude the necessary Autodesk hosts from the audit? Thank you very much.

[aloksard]

Hi,

Hope you are doing well.

As such we dont have Mcafee maintained list for this.

But domains mentioned in below link should be allowed:-

https://knowledge.autodesk.com/support/autocad/troubleshooting/caas/sfdcarticles/sfdcarticles/What-U...

https://knowledge.autodesk.com/search-result/caas/sfdcarticles/sfdcarticles/Supported-proxy-configur...

Was my reply helpful? If you find this post useful, Please give it a Kudos! Also, Please don't forget to select "Accept as a solution" if this reply resolves your query!

Regards

Alok Sarda

[alpha-soft]

Hello,

thanks for your feedback.

But what is the best way to implement it based on Autodesk's setup? Would it make sense to bypass the above URLs completely (stop cycle) or only for authentication? The second question would be, how do I best tinker the whitelist? For example, Autodesk names:
HTTP and HTTPS for
www.autodesk.com
access.clic.autodesk.com
clm.clic.autodesk.com
accounts.autodesk.com
api.autodesk.com
cur.autodesk.com

Would it be right in the MWG:

*autodesk.com
*access.clic.autodesk.com
*clm.clic.autodesk.com
And so on?

Or:
*.autodesk.com
*.access.clic.autodesk.com
*.clm.clic.autodesk.com

Or
*://*.autodesk.com
*://access.clic.autodesk.com
*://clm.clic.autodesk.com

I don't know how best to do it?!

Should I open a support call at McAfee?

Thanks.

[swilkens1]

Hello @alpha-soft ,

It really depends on which property is referenced in the rules. If you use the property "URL", this stores the full URL, including the protocol and path. However, these examples are all of URL hosts, which you can use the MWG property "URL.Host" (or, alternatively, URL.Domain for a wider application).

You should check out the following Best Practice which details the proper use of these with several examples. You should be able to quickly see how to apply them:

Understanding URL Related Properties 

For your examples, it looks as if either of these would be sufficient criteria to match:

"URL.Domain equals 'autodesk.com' " or

"URL.Host matches *.autodesk.com"    ; not both of these criteria combined, just one or the other.

Regarding bypassing globally (whitelist with Stop Cycle) vs bypassing authentication only, that is your decision based on what content you still want to filter/scan through MWG and what Autodesk requires to work through a proxy.

Please let me know if this helps or if you have other questions.

[alpha-soft]

Hello again,

Despite the exclusion of Autodesk's predetermined websites, the MWG still blocks Autodesk licensing. I have no idea why!

I'm going to have to open a support case.

Should I open an extra support case or can we open one right here?

[lcc]

Hello there,

Did you manage to resolve this issue. We have the same problem. We cannot activate autodesk license despite bypassing everything for a particular client IP.