I haven’t really messed with the clientless features before but there’s a need for some internal pages to be accessible externally now. Is Cisco’s Clientless SSL VPN access portal on the ASAs (5516-X in my case) up to the task these days? The client’s user interface looks very… Windows XP, like it hasn’t been updated since 2002. I published a few bookmarks through it and while basic static pages work ok, more “modern” ones with a lot of Javascript like Jira or Kibana don’t render most or all of the page. Is this ASA feature capable of presenting more sophisticated web pages?
So what do you mean by “externally”? Do you mean that you want your authenticated domain users, for example, to have access from domain machines while working from home?
Do you mean you want anyone from the internet to be able to connect to them? Or something in between?
As far as the Clientless web UI, that’s customizable. You can change most of it via the XML that’s exposed. There’s a whole Cisco document about it.
It sounds like you’re exposing state-oriented applications without understanding how they work. A lot of stuff like you’re describing maintains session state at the server or through opaque session data in any of a variety of means of client-side storage APIs. Those mechanisms aren’t compatible with sharing a link within the context of a session. You either have to work with the application vendor to find a compatible means of deep linking, or don’t deep link.