How does EAP Flexible Authentication via Secure Tunneling (EAP-FAST) work?
The EAP-FAST scenario works as follows. • The method processes a password change at single-sign-on (SSO) employing the method UI. • The method returns the eatCredentialsChanged attribute. • The supplicant indicates to the user that credentials have changed and requests the user to re-enter their credentials. • The supplicant re-enters the user credentials, and sends those credentials to the method. For more information on EAP-FAST, see EAP Flexible Authentication via Secure Tunneling (EAP-FAST).
Related Questions
- Along with RFCs 2138 and 2139, there are several addendum drafts that describe compulsory tunneling, signature attributes, and EAP. Are these supported in IAS?
- Does ACU support Extensible Authentication Protocol-Flexible Authentication via Secure Tunneling (EAP-FAST)?
- How does EAP Flexible Authentication via Secure Tunneling (EAP-FAST) work?
