Forum Discussion
Portal Access and Layerd VS
we (must) use a Layerd VS in front of a Multi Domain SSO page and now we whant to use a Web Application using Portal Access.
The Problem is that this Application uses the F5_Warper (cash-fs.js) and F5 generates a "wrong" Hostname in the injected ur_firepass_host variable because APM uses the protocol of the layerd VS (Port 80) and not from the front VS (443)
if(typeof(F5_flush)!=='function'){
var ur_firepass_host='http://FQDN';--> should be https://FQDN
var F5_HT_adm_enabled='1';
.....
We know that we can solve that when we also use a SSL Profile (Server) on the front VS and a SSL Profile (Client) on the layerd VS but we hope to find a better way to save the resources especially with the Portal Access.
Manipulation the server.network.protocol via Irule will not work.
- Stanislas_Piro2
Cumulonimbus
Does TLS terminaison is required on the front virtual server? Did you see this article or this code to manage tls sni routing to layered virtual servers?
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com