RSNA Preauthentication Guidelines
Collapse the table of content
Expand the table of content

RSNA Preauthentication Guidelines

Important  The Native 802.11 Wireless LAN interface is deprecated in Windows 10 and later. Please use the WLAN Device Driver Interface (WDI) instead. For more information about WDI, see WLAN Universal Windows driver model.
 

If the 802.11 station supports the Robust Security Network Association (RSNA) authentication algorithm, it might support RSNA preauthentication for infrastructure basic service set (BSS) networks. RSNA preauthentication is defined in Clause 8.4.6.1 of the IEEE 802.11i-2004 standard. For an overview of preauthentication, see RSNA Preauthentication.

In order to support RSNA preauthentication, the miniport driver must support the following:

OID_DOT11_PMKID_LIST

This object identifier (OID) is used to set or query the list of pairwise master key (PMK) identifiers (PMKIDs) used by the 802.11 station for RSNA preauthentication. Each PMKID in the PMKID list is referenced by the basic service set (BSS) identifier (BSSID) of the access point (AP).

The miniport driver returns the maximum size of its PMKID list when queried by OID_DOT11_EXTSTA_CAPABILITY. If the 802.11 station does not support preauthentication, the driver returns a list size of zero. Otherwise, the miniport driver must return a list size of three or more PMKID entries.

NDIS_STATUS_DOT11_PMKID_CANDIDATE_LIST

This media-specific indication is made by the miniport driver to request PMKIDs for APs that the 802.11 station can potentially roam to. When roaming, the 802.11 station uses the PMKID value for the AP's BSSID to authenticate with the AP.

The miniport driver typically makes the NDIS_STATUS_DOT11_PMKID_CANDIDATE_LIST indication following a scan operation if it detects the BSSID candidate list changes within the BSS network with which the 802.11 is connected. For more information about scan operations, see Native 802.11 Scan Operations.

The miniport driver should keep the frequency of these indications to a minimum. For example, the driver should not make an NDIS_STATUS_DOT11_PMKID_CANDIDATE_LIST indication if only one new entry was added to its BSSID candidate list. Instead, it must make the indication after the number of new entries inserted into its BSSID candidate list reaches a driver-specific threshold.

The 802.1X supplicant will do the following when the miniport driver makes an NDIS_STATUS_DOT11_PMKID_CANDIDATE_LIST indication:

  • Replace the contents of its PMKID candidate list with the list associated with the indication.

  • Take the intersection of its PMKID candidate list and the Master PMK Table, which stores PMKID values resolved from previous authentication or preauthentication operations. The operating system uses the results of the intersection to immediately issue a set request of OID_DOT11_PMKID_LIST to the miniport driver. If the intersection of the two lists results in an empty list, the operating system makes the set request to clear the driver's PMKID list.

The following figure shows the actions performed when the miniport driver makes an NDIS_STATUS_DOT11_PMKID_CANDIDATE_LIST indication.

Diagram illustrating the actions performed when the miniport driver makes an NDIS_STATUS_DOT11_PMKID_CANDIDATE_LIST indication

The 802.1X supplicant can initiate preauthentication to the entries in its PMKID candidate list. After it resolves a PMK for a BSSID in the candidate list, the supplicant adds the new PMKID entry to its Master PMK Table and issues a set request of OID_DOT11_PMKID_LIST to the miniport driver to update the 802.11 station's PMKID candidate list.

For more information about the 802.1X supplicant, refer to the IEEE 802.1X-2001 standard.

The miniport driver must clear its PMKID list if any of the following occurs:

 

 

Send comments about this topic to Microsoft

Show:
© 2016 Microsoft