Autodesk Vault SSL connection issue

Autodesk Vault SSL connection issue

ChSchmidt
Enthusiast Enthusiast
1,147 Views
3 Replies
Message 1 of 4

Autodesk Vault SSL connection issue

ChSchmidt
Enthusiast
Enthusiast

Hi all,

 

I have a problem to establish a SSL connection on a customers system.

Everthing works well with http.

The server has a valid Cert (FQDN and hostname), all configs and xmls changed to FQDN as usual.

When I tried the first connect via https the client and also the server log told me, that the client and the server don't use a common protocol, IIS default website worked well.

Turned out that if you use a DOTNET 4 to 4.5 application on a system (here the server) which has installed a higher version of DOTNET than 4.5, you have to enable strong encryprion in the registry for DOTNET 4.

After setting these keys I was able to connect with the Vault Explorer and also with the Vault Web Client, but not with Inventor, AutoCAD or MS Office. These applications told me, that they can't find the Data Management services on the host. Do the client addins use other protocols and ciphers than the Vault Explorer, or do they not support strong encryption at all?

 

Versions:

Autodesk Vault Professional 2018.3

Autodesk Inventor 2018.3.1

Autodesk AutoCAD 2018.1.2

Autodesk AutoCAD Mechanical 2018.0.1

 

Microsoft Windows Server 2016

Microsoft Windows 10 Enterprise 1803

 

Anyone any idea?

 

Best Regards

Christian Schmidt

0 Likes
Accepted solutions (1)
1,148 Views
3 Replies
Replies (3)
Message 2 of 4

ChSchmidt
Enthusiast
Enthusiast

Just an update and some insights:

The customers infrastructure is configured for perfect forward secrecy for encrypted connections (like SSL for Vault), and only TLS 1.2 ist supported, since this is the only trustable method at the moment.

The Vault Professional Client supports TLS 1.2 Connections, the CAD Client Addins for Inventor and AutoCAD only support TLS 1.0, which I can't figure out why there is a difference.

 

Does anyone know a way to force the CAD Addins to use TLS 1.2?

 

Best Regards

Christian Schmidt

0 Likes
Message 3 of 4

ChSchmidt
Enthusiast
Enthusiast

Just another update,

Autodesk Support replied to this forum entry and opened up a support case.

The behaviour described above was marked as an incident and was transferred to the developement team.

 

Big Thanks @ Autodesk Support!!!

Best Regards

Chris

0 Likes
Message 4 of 4

ChSchmidt
Enthusiast
Enthusiast
Accepted solution

Good News from Richard Rankin!!!

The issue has been solved in following Versions of Vault:

 

Vault 2018.3.4
Vault 2019.3
Vault 2020.1 Update

 

I will test this in an strictly TLS1.2 environment, and will accept this as a solution.

 

BR

Chris

0 Likes