09-12-2019 05:36 AM - edited 02-21-2020 09:29 AM
We have 2 pairs of HA 2110 Security Appliances managed from an FMC all running 6.4.0.2 currently trying to get kerberos working
All seems correct and in place joined AD, LDAPS, ACL Rule, SSL rewrite policy, Identity Policy configured with a cert using default port 885
Browsing to a site causes a redirect to the correct FQDN (DNS Resolves) of the FTD to authenticate and this is when it fails can not connect
nmap shows as closed (Firewall ACL to allow is there)
Logging into FTD and running in expert mode
netstat -anp | grep 885
gives
tcp 0 0 169.254.0.1:885 0.0.0.0:* LISTEN 21645/idhttpsd
tcp6 0 0 fdcc::bd:0:ffff:a9f:885 :::* LISTEN 21645/idhttpsd
Not listening on expected IP?
Also output from vhost.conf shows
Listen 169.254.0.1:885
Listen [fdcc:0000:0000:00bd:0000:ffff:a9fe:1]:885
<VirtualHost 169.254.0.1:885 [fdcc:0000:0000:00bd:0000:ffff:a9fe:1]:885>
# This ServerName option might not be required at all after LTB is in place.
# Needs to do some tests to verify after LTB is available. Put localhost here for now.
ServerName localhost
SSLCertificateFile "/ngfw/usr/local/sf/idhttpsd/conf/auth.cert"
SSLCertificateKeyFile "/ngfw/usr/local/sf/idhttpsd/conf/auth.key"
AuthFormPath "/ngfw/usr/local/sf/idhttpsd/conf/auth_form.html"
EncryptionBytesPath "/ngfw/usr/local/sf/idhttpsd/conf/captive_portal_url_encryption_bytes.bin"
ErrorLog "/ngfw/var/log/captive_portal.log"
LogLevel info
SSLEngine on
LoadModule auth_module modules/mod_sfcaptive_portal.so
AddHandler auth-handler auth
DocumentRoot "/ngfw/usr/local/sf/idhttpsd/captive_doc"
<Directory "/ngfw/usr/local/sf/idhttpsd/captive_doc">
Require all granted
SSLRequireSSL
</Directory>
</VirtualHost>
ServerName localhost
Nothing I can find in FMC to set which IP/interface to use only port any thoughts or is this a known issue (Can not find any fix only the latest release)
10-09-2019 08:37 AM
I have the very same problem but on ASA 5515-X v.9.12.2.4 with Firepower 6.0.4.5.
The users are recognized by Passive Auth, but if it fails it fallbacks to active auth and in this case the captive portal is not reachable. The clients tries to connect with the management IP Address of the Firepower module, but the captive portal is listening only on the tun1 interface.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide