alexmJH
(Alex Moritz)
November 11, 2024, 10:06am
1
1. The problem I’m having:
I’m trying to reverse proxy an application server that does Kerberos authentication for handling single sign on. When doing so with Caddy SSO doesn’t work.
When doing the same with an F5 appliance automatic logon (SSO) is possible.
2. Error messages and/or full log output:
No notable logging
3. Caddy version:
2.7.6
4. How I installed and ran Caddy:
RHEL8 server with caddy installed natively
a. System environment:
d. My complete Caddy config:
myurl.mydomain.net {
log {
output file /var/log/caddy/myurl.log
}
reverse_proxy hostname.domain:8090 {
}
tls "/etc/ssl/certs/caddy/certificate.cer" "/etc/ssl/certs/caddy/certificate.key" {
}
}
alexmJH
(Alex Moritz)
November 11, 2024, 11:57am
3
Aren’t Kerberos and NTLM different protocols/standards?
I don’t know anything about Microsoft’s protocols. It’s all a black box to me.
1 Like
ATFBooru
(ATFBooru)
November 26, 2024, 7:51pm
5
alexmJH:
1. The problem I’m having:
I’m trying to reverse proxy an application server that does Kerberos authentication for handling single sign on. When doing so with Caddy SSO doesn’t work.
When doing the same with an F5 appliance automatic logon (SSO) is possible.
2. Error messages and/or full log output:
No notable logging
3. Caddy version:
2.7.6
4. How I installed and ran Caddy:
RHEL8 server with caddy installed natively
a. System environment:
d. My complete Caddy config:
myurl.mydomain.net {
log {
output file /var/log/caddy/myurl.log
}
reverse_proxy hostname.domain:8090 {
}
tls "/etc/ssl/certs/caddy/certificate.cer" "/etc/ssl/certs/caddy/certificate.key" {
}
}
Caddy likely lacks Kerberos pass-through support. Use F5 for SSO or explore Caddy plugins like caddy-auth-portal for alternatives.
alexmJH
(Alex Moritz)
December 12, 2024, 2:05pm
6
After spending hours and even trying Apache we finally figured it out…
You can’t use a CName when trying to do Kerberos. That causes the client to fallback to NTLM.
After changing the CName to an A-Record everything works fine now