Binding an 802.1X Access Profile to the Authentication Profile

This section provides a sample of binding an 802.1X access profile to the authentication profile using the merge method. You can also use the create method to bind an 802.1X access profile to the authentication profile.

**Table 1** Binding an 802.1X access profile to the authentication profile
Operation	XPATH
edit-config:merge	/huawei-nac:nac-access/configure-mode/unified-mode/authentication-profile/dot1x-access-profile

Data Requirement

**Table 2** Binding an 802.1X access profile to the authentication profile
Item	Data	Description
dot1x-access-profile	dot1x_access_profile	Bind the 802.1X access profile dot1x_access_profile to the authentication profile authen_pro. The 802.1X access profile must exist on the switch.

Request Example

<rpc xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_012824316d704d43adb16b1a4245d273">
 <edit-config>
  <target>
   <running/>
  </target>
  <error-option>rollback-on-error</error-option>
  <config>
   <nac-access xmlns="urn:huawei:params:xml:ns:yang:huawei-nac">
    <authentication-profile xmlns:ns0="urn:ietf:params:xml:ns:netconf:base:1.0" ns0:operation="merge">
     <name>authen_pro</name>
     <dot1x-access-profile>dot1x_access_profile</dot1x-access-profile>
    </authentication-profile>
   </nac-access>
  </config>
 </edit-config>
</rpc>

Response Example

Sample of successful response

<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="DEVICECONFIG_012824316d704d43adb16b1a4245d273">
 <ok/>
</rpc-reply>

Sample of failed response

<?xml version='1.0' encoding='UTF-8'?>
<rpc-reply xmlns="urn:ietf:params:xml:ns:netconf:base:1.0" message-id="47">
  <rpc-error>
    <error-app-tag>-1</error-app-tag>
    <error-message>config/undo access profile failed</error-message>
    <error-info>Error on node /huawei-nac:nac-access/authentication-profile[name="authen_pro"]/dot1x-access-profile</error-info>
  </rpc-error>
</rpc-reply>