Leveraging BIG-IP APM for seamless client NTLM Authentication
Many customers express interest to use F5 Access Policy Manager for transparent seamless authentication for their users. There are a couple of leading use cases that drive that desired behavior:
...
@michael - this is not the biggest problem for me. Currently i have the problem that the external logon URI needs to be FQDN.
How can I do that dynamically depending on the used URL for the client? e.g. i cannot include library.company.com there because all my logins to the URL sharepoint.company.com will in this case be redirected to the inserted external Logon Page information...
There must be something to dynamicall use a specific variable or something to get this topic closed...
Our Sharepoint has seven different URLs...
intranet/customer-service/myhome/etc.
Does this means I need to use another virtual server, which means another Public IP for each of these DNS names to accomplish my wished goal? Or what do you mean with "use two access sessions" here?