@PhoneBoy wrote:
R&D does.
Custom Application/Sites are meant to match URLs, not just hostnames, which are naturally a little more complicated.
I figured. Unfortunately the situation I face is that I have protected networks that are not allowed external internet traffic except for applications that need to reach their hosted SaaS provider (since everything is going cloud). Ideally I'd want to do this via the security policy and use of hosts/networks, but it's impossible when some of these providers are using backend providers like AWS and suggest we open ourselves up to entire /8 - /16 networks because they cannot give us specific dedicated hosts or they simply ask us to whitelist their domains.
As such I've had to resort to allowing outbound to the internet in Security policy and try to further limit it via Application policy, which leads me to where I'm at now.
I simply want to allow access to domain1.com, domain2,com, etc. I'm just running into issues doing this because I don't want to open it up to JUST https://domain1.com (and have something like https://app.domain1.com/somedir/somepage.html being blocked because the interface isn't clear as to how to properly enter criteria to match what I need. The guide suggests use of wildcards, but the UI won't allow me to type them in as suggested, hence the problem that lead me here.