Further, while this internal back-end server isn't going to have any external traffic hit it directly, it's definitely going to need internet access to your Workspace One SaaS instances, just as with your front-end appliance. You'll need to allow the back-end appliance to receive this traffic, as well as ensure it has connectivity to any of the targeted internal resources. Finally, it's going to pass traffic to the back-end server over 4. Also, it will need to have internet access to your Workspace One SaaS instance over 443. Accordingly, the setup and traffic flow looks like this:įor your front-end appliance you'll need ports 4 opened up to it's external interface. However, it's recommended to go ahead and leverage 443 for Per-App VPN traffic. The above diagram applies to Cascade mode deployments that use default ports.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |