Refer to the exhibit. A mobile station in a factory contains an AP configured as a work group bridge that authenticates to a root AP using EAP-FAST. To be able to use the mobile station in further…

Although both RAPs are configured for EAP-FAST, the successful authentication with RAP1 and subsequent failure with RAP2 implies a mismatch in their specific EAP-FAST parameters or how they interact with the authentication server. This functional difference, such as mismatched Protected Access Credentials (PACs) or inconsistent backend server policies for RAP2, effectively makes the 'protocol' behave differently for the workgroup bridge.

If RAP2 had a different SSID, the mobile station configured as a workgroup bridge would likely not attempt to roam to it or would fail association, not just authentication.

EAP-FAST is an authentication protocol; while it establishes keys for encryption, a mismatch in the encryption type (e.g., AES vs. TKIP) is distinct from the authentication protocol itself and would manifest differently.

If the authentication username and password were truly different for the same workgroup bridge, it would likely fail authentication with RAP1 as well, assuming the WGB uses consistent credentials.