Using Okta Access Gateway with Windows File Shares
Last Updated:
Access Gateway
Overview
Okta Access Gateway (OAG) does not natively support direct interaction with Windows file shares because Okta only proxies HTTP and HTTPS connections. A workaround exists to force users to download all files over HTTP by configuring the file shares as virtual directories in Internet Information Services (IIS).
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Okta Access Gateway (OAG)
Cause
Okta Access Gateway (OAG) does not natively support direct interaction with Windows file shares. Okta only proxies HTTP and HTTPS connections.
Solution
How can Okta Access Gateway be configured to work with Windows file shares?
Configure the Universal Naming Convention (UNC) file shares as virtual directories in Internet Information Services (IIS) and integrate Okta Access Gateway with IIS via Kerberos to allow file downloads over HTTP without a VPN.
- Configure the UNC file shares in IIS as virtual directories.
- Enable Windows security on the IIS virtual directories and integrate OAG with IIS via Kerberos.
