This message was deleted.
# citrix-netscaler
s
This message was deleted.
j
Sounds like the wrong type of bookmark url. Also check if the domain is in the list for cvpn.
j
It sounds like you didn't add the FQDN you want to reverse proxy in the bind policy set latest ns_cvpn_default_inet_domains When I publish a bookmark using -clientless ON -applicationtype CVPN it works. Bear in mind support is limited for this, many apps are not reversed correctly. Citrix is now investing in Citrix Secure Private Access (SPA).
j
The bookmark url is correct and works fine in the internal network. What do you mean by the list for cvpn? Is it the: configure domains for clientless access list?
I see, it is a patternset. Yes the URL in the patternset. By changing the applicationtype to cvpn, it will continue to the page. Unfortunately I will get a blanc page. Could it something to do with the limited support you write about?
j
yes most likely it is not compatible with your web app. If you can see a correct rewrite in the URL and it doesn't load correctly then it's not compatible. You may fix it but it's tricky.
j
Ok, that makes sense. I will return this to application owner. Thank you both!
l
a way to do it with a lot more compatibility is not using cvpn, but using the same content switch as your unified gateway to publish the resources externally, then putting AAA in front of it pointing back to your Unified gateway, you can then put bookmarks that will open a tab with a publicly accessible url, not cvpn'ed with full functionality
so that if you directly go to the appurl, you'll get redirected to your gateway for authentication and then to the app, or if you log into your gateway, you'll get the app portal with all bookmarks that won't prompt you for auth again
the pain comes after that if you want to SSO into those apps ... 🙂
j
Interesting, I don't think it can work with all apps like the one not using relative path, etc. but that's an option too. Also it is possible to tune the CVPN to avoid rewrite for some specific URL. Prob is really about bad web app making weird calls.
k
I've done the same as @Lucas Van den Broeck, rewrites work more reliable when you only rewrite the hostname and possibly the protocol, not the whole URL
SSO is another discussion, but at least for many basic auth web servers it's doable (especially with standard 401), forms based gets trickier
j
That's good to know, I'll try it next time I have an app to publish!
j
I will take that as an option as well. Thanks!