On Oct 28, 2026, at 10:33 AM, Alexander Clouter via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
On a related note, it is a real crime Google, Apple and Microsoft completely undermined EAP-GTC[3] and do not show the challenge message and cache the response as a static credential. We could have all gotten easy access to MFA.
No one at those companies gets promoted for making Wi-Fi easier to use. So Wi-Fi has been a disaster for coming on 20 years.
The bigger issue with resumption is that most people consider "TLS resumption == authentication + authorization" when really it is neither and all it _reliably_ does is established a TLS jacket faster.
I'm trying to change that in https://datatracker.ietf.org/doc/draft-dekok-emu-tls-tickets/ There is interest from hostap && Cisco. Separating TLS resumption from inner authentication can also help enormously with PQC certificates. Those certs are large, and might need 80 round trips (!). For someone roaming in eduroam, this could mean that authentication takes 6 seconds or more.
TTLS for TLS 1.2 (RFC5281, section 7.5) makes the server responsible for making "resumption == authentication" and no authentication related traffic may occur in the tunnel for a resumed session. In an, albeit easy to pick apart as are we really saving here, argument a user that changed their password recently or mistyped it the first time has to restart the TLS jacket from afresh. For TLS 1.3 (RFC9427, section 4), you are allowed to redo the inner methods after resumption....no idea if supplicants actually support this though.
hostap supports this, sort of. My draft above tries to find ways to do this automatically, without breaking interoperability with legacy supplicants.
For authorization, you as the admin must drag out and duplicate the important parts of your inner-tunnel authorization section to either your outer post-auth[5] section or your tls-cache 'load' section. Not the end of the world, but something the FR codebase recently highlighted[6] so hopefully the message gets out there.
We're working on getting that fixed. Or at least, making it a lot easier to use. Alan DeKok.