• All
  • Test
  • Startup
  • Experience Case
  • FAQ
Product line
Search
Cancel
Documents type
Author
Time
Search

Local dot1x authentication failed

2021-12-27 17:16:49 Published
  • 0Followed
  • 0Collected ,61Browsed
fans:0 follow:0

Network Topology

Problem Description

Local dot1x authentication failed.

The configuration is as follows:

#
interface GigabitEthernet1/0/1
 port link-mode bridge
 port access vlan 10
 dot1x

#
local-user H3C class network
 password cipher $c$3$JjIBZPmVTxhKyzloh/rhr+iCneTHq9kgVFpFs0up
 service-type lan-access
 authorization-attribute user-role network-operator
#

Process Analysis

1. Check the on-site configuration and found that dot1x is not enabled in the system view.

For 802.1X to take effect on a port, you must enable it both globally and on the port.

#Enter system view.

system-view

#Enable 802.1X globally.

dot1x

#By default, 802.1X is disabled globally.

2. After dot1x is enabled globally, the authentication still fails. At this time, it is found that the user name in the 802.1X client used is h3c, and the device is configured with H3C, and the case is different.

The user name needs to be case-sensitive, with the following specific requirements.

user-name: Specifies the local user name, a case-sensitive string of 1 to 55 characters. The name must meet the following requirements:

·     Cannot contain a domain name.

·     Cannot contain any of the following characters: forward slash (/), backslash (\), vertical bar (|), colon (:), asterisk (*), question mark (?), left angle bracket (<), right angle bracket (>), or at sign (@).

·     Cannot be a, al, or all.

3. After modifying the user name in the 802.1x client to be consistent with the device configuration, the authentication succeeds.



Solution

1. Enable dot1x globally 

2. Note that the user name is the same as the one configured on the device

3. If  an iNode client is used, to ensure that the local authentication can be successfully performed, make sure that the "Upload version info" option in the 802.1X connection properties is not selected.



Please rate this case:   
0 comments

No comments

Add Comments:

举报

×

侵犯我的权益 >
对根叔知了社区有害的内容 >
辱骂、歧视、挑衅等(不友善)

侵犯我的权益

×

泄露了我的隐私 >
侵犯了我企业的权益 >
抄袭了我的内容 >
诽谤我 >
辱骂、歧视、挑衅等(不友善)
骚扰我

泄露了我的隐私

×

您好,当您发现根叔知了上有泄漏您隐私的内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到zhiliao@h3c.com 邮箱,我们会尽快处理。
  • 1. 您认为哪些内容泄露了您的隐私?(请在邮件中列出您举报的内容、链接地址,并给出简短的说明)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)

侵犯了我企业的权益

×

您好,当您发现根叔知了上有关于您企业的造谣与诽谤、商业侵权等内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到 zhiliao@h3c.com 邮箱,我们会在审核后尽快给您答复。
  • 1. 您举报的内容是什么?(请在邮件中列出您举报的内容和链接地址)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)
  • 3. 是哪家企业?(营业执照,单位登记证明等证件)
  • 4. 您与该企业的关系是?(您是企业法人或被授权人,需提供企业委托授权书)
我们认为知名企业应该坦然接受公众讨论,对于答案中不准确的部分,我们欢迎您以正式或非正式身份在根叔知了上进行澄清。

抄袭了我的内容

×

原文链接或出处

诽谤我

×

您好,当您发现根叔知了上有诽谤您的内容时,您可以向根叔知了进行举报。 请您把以下内容通过邮件发送到zhiliao@h3c.com 邮箱,我们会尽快处理。
  • 1. 您举报的内容以及侵犯了您什么权益?(请在邮件中列出您举报的内容、链接地址,并给出简短的说明)
  • 2. 您是谁?(身份证明材料,可以是身份证或护照等证件)
我们认为知名企业应该坦然接受公众讨论,对于答案中不准确的部分,我们欢迎您以正式或非正式身份在根叔知了上进行澄清。

对根叔知了社区有害的内容

×

垃圾广告信息
色情、暴力、血腥等违反法律法规的内容
政治敏感
不规范转载 >
辱骂、歧视、挑衅等(不友善)
骚扰我
诱导投票

不规范转载

×

举报说明

提出建议

    +

Login before you can operate!

login

你的邮箱还未认证,请认证邮箱或绑定手机后进行当前操作