We're encountering problems with users not able to post/edit/delete when logged in, and we've traced some of this to domB being case-sensitive with usernames, whereas in our testing, Domino is not. No matter how a username is typed for login, Domino accepts the login, and domB displays "you are logged in as" username as currently capitalized in the NAB.



The problem is, username capitalization sometimes gets changed, but we find domB JavaScript username comparisons that assume identical case. This is critical because domB does various things based on the username of a posted message matching the current logged-in username.



We have many users who created usernames with mixed case. But since the username is displayed by DomB as the user's name (rather than their real name from the NAB), users sometimes request that capitalization be changed for better display, such as bigbubba changed to BigBubba. This doesn't affect Domino login, but in domB it seems to disconnect the old username from the new username.



Our half-solution is to modify code in common.js to force lowercase comparisons via username.toLowerCase(). This mostly continues to display the real case of username, but forces domB to be case-insensitive for comparisions. But this is a risky hack; it's difficult to locate all the instances of username comparision, and to be sure something else isn't being broken by our "fix". And further confusing us, on some screens we see real capitalization in one place, but lowercase in another; we don't think this is due to our code change, but "maybe"?



It's not practical to change the original created-by username stored by Domino in each posted message when a username's NAB capitalization is changed. This isn't necessary for Domino, so it shouldn't be necessary for a Domino application.



We request that domB handle usernames like Domino, case-insensitive so behavior is consistent.