blocks|key|361230|text|不，这不是默认的bug。这取决于系统的需求，在这种情况下没有全局规则。有些操作系统允许同一个用户使用不同的大小写。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|361231|即使是email+adress+(username@hostname.tld)的用户部分也不是在所有情况下都区分大小写。有关更多信息，请参见关于堆栈溢出的问题电子邮件地址是否区分大小写？。|offset|length|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/9807909/are-email-addresses-case-sensitive^0|0|27|E|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]]|F|$G|$5|H|I|J|A|$K|L]]]]

No, it's not a bug by default. This depends on the requirements of the system, there is not global rule for situations like this. Some operating systems allow the same user with different casing.

Even the user part of an email adress (username@hostname.tld) is not case sensitive in all cases. For more info see the question <a href="https://stackoverflow.com/questions/9807909/are-email-addresses-case-sensitive">Are email addresses case sensitive?</a> on Stack Overflow.

blocks|key|2195496|text|在我看来，检查大小写敏感性本身并不是一个错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2195497|如果用户不知道用户名是区分大小写的，我会认为它是一个bug。否则，人们可能会感到奇怪，为什么他有时可以很好地登录(username1)，有时会收到错误消息(Username1)。在其他情况下，区分大小写用于向安全性添加额外(但非常薄)层。|2195498|出于可用性原因，如果用户名区分大小写，则不应允许创建同名但大写不同的帐户。这部分我肯定会认为是个小虫子。|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|H|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|I|8|@]|9|@]|A|$]]]|F|$]]

Checking for case sensitivity itself isn't a bug in my opinion.

I'd consider it a bug, if the user doesn't get informed about the username being case sensitive.
Otherwise one may wonder, why he sometimes can log in fine (Username1) and sometimes gets an error message (username1).
In other cases the case-sensitivity is used to add an extra (but very thin) layer to the security.

For usability reasons, if a username is case sensitive it shouldn't be allowed to create accounts with the same name but different capitalization.
This part I'd definitely see as a bug.

blocks|key|361354|text|我认为这是一个可用性/UX的问题。我认识的大多数服务都使用不区分大小写的登录，而我认识的大多数人使用区分大小写的登录来指责服务。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|361355|因此，我想说，您应该检查需求，并根据结果，咨询BA/PO/PM或项目中的任何人，并询问他(+a)是否有人考虑过登录大小写敏感性和(+b)哪个选项是正确的。|361356|如果要求说它应该是大小写敏感的，你也可以与你的经理交谈，问他为什么认为应该如此，并分享你对这件事的看法。|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|H|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|I|8|@]|9|@]|A|$]]]|F|$]]

I'd consider this as a matter of usability/UX. Most services I know use case-insensitive logins, and most people I know use to blame services with case-sensitive logins.

So, I'd say you should check the requirements, and, depending on the result, consult with BA/PO/PM, or whoever you have on the project, and ask him a) if anyone ever thought about login case-sensitivity and b) which option would be correct.

If requirements say it should be case-sensitive, you can also talk to your manager, ask him why he thinks it should be so and share your opinion on the matter.

blocks|key|361403|text|没有标准的规则。每个应用程序都决定如何处理用户名，以及是否需要区分大小写。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|361404|如果您的应用程序应该区分大小写，并且不敏感，那么这就是一个bug。如果它不应该区分大小写，那就是一个bug。|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|F|8|@]|9|@]|A|$]]]|D|$]]

There is no standard rule. Every application decides how to handle user names and whether case sensitivity is needed/wanted.

If your application is supposed to be case-sensitive and isn't, that's a bug. If it's not supposed to be case-sensitive and is, that's a bug.

blocks|key|361154|text|对于用户名，它不区分大小写，因此user2+=+useR2+=+USER2，但在密码情况下，这些密码是3个不同的密码，因为密码将被加密。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

In case of username it isn't case-sensitive so user2 = useR2 = USER2
but in password case those are 3 different passwords because password will be encrypted.

blocks|key|361267|text|我同意尼尔斯的观点。这不能仅仅基于能够创建不同大写字母集的帐户而被认为是一个错误。您应该参考这些要求，看看在创建帐户的情况下，它是否具体区分了大写和小写。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|361268|在这种情况下没有检查规则。对于Gmail，您可以使用USERNAME@gmail.com和username@gmail.com登录。它不能被认为是一个bug。|offset|length|style|CODE|entityMap^0|0|Q|I|19|I^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|J|8|@$D|K|E|L|F|G]|$D|M|E|N|F|G]]|9|@]|A|$]]]|H|$]]

I agree with @Niels. This cannot be considered as a bug, solely on the basis of being able to create accounts with different set of upper case letters. You should refer to the requirements, to see if it specifically distinguishes between upper case and lower case in case of account creation.

There is no rule to check in this scenario. For Gmail allows you to log in using <code>USERNAME@gmail.com</code> as well as <code>username@gmail.com</code>. It can't be considered a bug.

blocks|key|361501|text|从UX的角度来看，用户名不应该区分大小写。通过暴力攻击获得的边际收益不会抵消增加的UX复杂性，以至于开发人员无法对用户可能犯的错误进行QA。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|361502|例如，我甚至搜索并找到了这条讨论线索。我正在使用Axis相机，它和许多IP相机一样，基本上是一个嵌入式web服务器。这些设备允许多个帐户，我们为服务人员创建了其中一个帐户。出于打字习惯，我无意中创建了一些这些帐户的初始上限。我没有收到警告说用户名是区分大小写的。|361503|当服务人员无法登录时，我意识到他们使用的是用户名的所有小写版本。没问题，我想，只是一种烦恼。但是，当我试图删除“用户名”并创建“用户名”时，我遇到的用户已经存在错误，即使用户实际上并没有被列出。我可以添加一个大小写敏感版本的用户，但是要添加小写版本，我必须将设备重新设置为工厂默认值，以清除user表中的错误条目。|361504|由于这一点和许多其他原因，Windows用户名不区分大小写，这就是为什么所有COTS用户名都不区分大小写。如果您的需求指定区分大小写的用户，或者根本不指定用户大小写敏感性，那么您的需求可能是错误的，从专业角度讲，请大声说出来。如果有明确的理由让本地开发的解决方案具有区分大小写的用户名，那么就准备承担大量额外的测试和用户支持费用。|361505|幸运的是，我只在10个摄像头上这样做，而不是全部2000年，所以我只需要几个小时的额外工作和服务缺口，这10个相机需要默认，但我可以很容易地使用供应商的工具，以创建资本用户名，然后我将不得不默认我们整个工厂。|361506|没有真正的好处，区分大小写的用户名，我可以看到，一些巨大的缺点，因为额外的错误测试和用户不满时，不可避免的错误击中了生活的挡风玻璃。|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|O|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|P|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Q|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|R|8|@]|9|@]|A|$]]]|L|$]]

From a UX perspective usernames should NEVER be case sensitive. The marginal gains against brute force attacks do not offset the added UX complexity to the point where a developer cannot QA against the possible mistakes a user can make.

Case in point is the reason that I even searched for and found this discussion thread. I am working with Axis cameras which like many IP cameras is basically an embedded web server. These devices allow for multiple accounts one of which we create for our service folks. Out of typing habit I accidentally created a number of these accounts with an initial cap. I received no warning that usernames are case sensitive.

When the service person could not login I realized that they use the all lowercase version of the username. No problem, I think, just an annoyance. But when I try to delete the "Username" and create the "username" I am met with a user already exists error even though the user is not actually listed. I can add a user with the case sensitive version just fine but to add the lower case version I have to reset the device back to factory defaults to clear out the bad entry in the user table.

For this and many other reasons, Windows usernames are case insensitive and this is why ALL COTS usernames should be case insensitive. If your requirements specify case sensitive users or do not specify user case sensitivity at all, then your requirements are likely wrong and professionally speaking, speak up. If there is a clear justification for a locally developed solution to have case sensitive usernames then be prepared to significant additional testing and user support costs. 

Fortunately I only did this on 10 cameras and not all 2000 so I only have a few hours of extra work and service gaps on the 10 cameras that need defaulting but I could just as easily have used the vendor tools to create the capital Username and then I would be having to default our entire plant. 

There is NO real upside to case sensitive usernames that I can see and some huge downsides with regard to additional bug testing and user dissatisfaction when the inevitable bugs hit the windshield of life.

blocks|key|361530|text|取决于用例。但是，如果公共用户名允许大小写，您可以通过大写一个或多个字母来让某人模仿知名用户。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|361531|用户名'presidenT‘看起来像’总统‘，’总统‘或’总统‘。|361532|我建议与产品负责人讨论这个问题，并提倡使用区分大小写的密码。|361533|由于密码是个人的，不显示，大小写允许更多的组合和排列。|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|J|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|K|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|L|8|@]|9|@]|A|$]]]|H|$]]

Depends on the use case. However, if public usernames allow case, you can have someone impersonate a well-known user by just capitalizing one or more letters.
The username 'president' look like 'presIdent' or 'President' or 'presidenT'.
I would recommend discussing this with the product owner and advocating for case-insensitive usernames, with case-sensitive passwords.
Since passwords are personal and not displayed, case allows for more combinations and permutations.

blocks|key|2195582|text|在我使用的大多数主要站点中，我发现密码中的大小写敏感性是一个标准功能。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2195583|实际上，在他们中的许多人中，密码要求经常包括“大写字母和小写字母”，要做到这一点，密码本身就必须区分大小写。|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|E|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|F|8|@]|9|@]|A|$]]]|D|$]]

I find case-sensitivity in passwords to be a standard feature in most of the major sites that I use.

Indeed in many of them the password requirements frequently include "both an upper and lower case letter" and for that to work obviously the password must be case-sensitive itself.

blocks|key|2195653|text|我相信这要视乎情况而定。大型外部网站应该是不区分大小写的，例如Gmail。但是，如果网络应用程序或应用程序只是某个公司使用的内部应用程序，那么它应该是区分大小写的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|entityMap^0^^$0|@$1|2|3|4|5|6|7|C|8|@]|9|@]|A|$]]]|B|$]]

I believe it should depend on the situation. Large external websites should be case insensitive like for instance Gmail. But if the web app or application was a internal app used just by a certain company then it should be case sensitive.

I need to know what is the standard rule for creating username/login ID. Should it be case-sensitive? If I have successfully created three accounts (user2, useR2, USER2), should I consider this a bug?

Should username/login ID be case-sensitive?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我需要知道创建用户名/登录ID的标准规则是什么。它应该区分大小写吗？如果我已经成功地创建了三个帐户(user2，useR2，USER2)，我是否应该认为这是一个bug？

问用户名/登录ID应该区分大小写吗？
EN

回答 10

Stack Exchange QA用户

Stack Exchange QA用户

Stack Exchange QA用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问用户名/登录ID应该区分大小写吗？EN

回答 10

Stack Exchange QA用户

Stack Exchange QA用户

Stack Exchange QA用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问用户名/登录ID应该区分大小写吗？
EN