Incorrect type of SSL VPN virtual gateway cause cannot access SVN web via https

Publication Date:  2013-07-30 Views:  216 Downloads:  0
Issue Description
Client access SSL VPN wb page via https://x.x.x.x. There is a wrong page when click  "continue to this website (not recommended), the page
Alarm Information
None
Handling Process
1. check the configuration in current network, the virtual gateway type is sharing
v-gateway sslvpn x.x.x.x public test.com
2. modify the configuration as below:
v-gateway sslvpn x.x.x.x private test.com
3. Test again, and the SSL VPN function goes through.
Root Cause
SVN support exclusive virtual gateway and sharing virtual gateway.
1. An exclusive virtual gateway occupies the IP address and domain name exclusively. Users can access an exclusive virtual gateway through its domain name or IP address.
2. Sharing virtual gateways share the same IP address, Users can access a sharing virtual gateway only through its domain name.
The domain names of sharing virtual gateways are identified in the following ways:
If the parent domain names are the same, distinguish the domain name based on the sub-domain name. For example, the domain name for the sharing virtual gateway aaa is www.abc.com/aaa, the domain name for the sharing virtual gateway bbb is www.abc.com/bbb.
Only the first nodes of the domain name are different. For example, the domain name for sharing virtual gateway aaa is a.abc.com, the domain name for sharing virtual gateway bbb is b.abc.com.

Suggestions
It's necessary to understand the difference between exclusive and shared virtual gateway, and it should be configured according to the actual sceranio.

END