Kerberos absolutely works through NAT.
I used it to connect to campus servers back in college, through my home NAT.
There is an optional field in the Kerberos ticket that can contain your client address, as an additional point of validation to prevent certain classes of replay attack. That particular feature can conflict with NATs. But it's optional.
Re:Explain like I’m 5: Kerberos (2013)
by youdontknowtho on Tuesday June 27, 2017 @10:49AM
(#14645882)
Touche. As one other commenter pointed out, it's naming that can be difficult with NAT and that can break Kerberos. Good point.
"Kerberos doesn't work through NAT"
I can access my email via Evolution EWS through external name -> NAT -> (good TLS) HAProxy (rubbish SSL) -> Exchange 2016 using Kerberos auth.
Yeah, Kerberos can generally work across NAT, but DNS complexity often makes it not worth the trouble.
Re:Explain like I’m 5: Kerberos (2013)
by youdontknowtho on Tuesday June 27, 2017 @10:48AM
(#14645869)
Good point. It's naming that often breaks in NAT. And it's naming that is almost always what breaks Kerb. Cheers.
Open ID Connect will support the more complicated "delegation" scenarios that Kerberos enabled. Think, authentication across multiple service boundaries. That kind of thing.