We're looking into replacing a customer's existing SSL solution with an ASA-based clientless SSL, but we're coming up against a thorny issue: the customer has different customized portals each tied to a completely separate domain name and certificate but hosted on the same SSL appliance. Example:
From what I can see, the ASA can only support one server-side certificate per interface, so we would need multiple interfaces to do this. Not pretty, but doable: set aside a /24 and use multiple /30 vlans between the ASA and the Internet switch, for example.
My challenge though is that how can I route back to the same destination (say, the Internet) over distinct interfaces? I can't have the default route pointing back to two distinct locations with the same cost.
I thought that the ASA could potentially treat connections to itself (after all, it is hosting the SSL portal) differently, but could not find any authoritative information about it. Is this where the identity interface comes into play?