Vault Gateway FAQ

Refer to these Frequently Asked Questions (FAQ) to better understand how the Vault Gateway works.

How secure is the connection from the Vault Gateway to the Vault Server?

What information is stored in the Vault Gateway?

What Vault authentication methods can be used with Vault Gateway?

What kind of Denial-of-Service attack protection is in the Vault Gateway service?

How do I get a license if I use the Vault Gateway and not on my network?

Can I use SSO with Vault Gateway?

What are the password requirements needed to use Vault-authenticated accounts with the Vault Gateway?

Is data encrypted during transit?

Can we limit who can use the Vault Gateway service?

What has to be installed on the client workstations to use the Vault Gateway?

Will all Vault clients and add-ins be able to use the Vault Gateway?

Does the Vault Gateway support multifactor authentication?

Can this be put on a different server in the DMZ and communicate with our Vault client on-prem?

Reporting - Can we tell where users are connecting from (regions as an example)?

Are there other IP type restrictions that we could implement to make this more controllable on our end?

How is the Vault Gateway itself secured?

Is the Vault Gateway located within the continental US?

Can the location of the Vault Gateway be configured?

Does the Vault Gateway store any data or metadata?

Does the gateway mechanism support integration with OKTA identity management?

Is it a single-tenant environment, for example where each customer receives a dedicated cloud virtual machine?

Does Autodesk perform any penetration or vulnerability testing on Vault Gateway?

What are the Vault Server firewall requirements to connect to the Vault Gateway?