Community
RU Server Usernames should be case-insensitive
Links used in this discussion
Links used in this discussion
Marty,
User (Posts: 7)
Jul 17, 2018 3:06:19 am EDT
Support level: Free or trial
I'm using RU server 2.6.0.3 and Host/Viewer 6.8.0.1
I found when configuring a host to use Custom Server Security, the capitalization of the username matters. For example, logging on with username "johndoe" will fail if the username on the server is "JohnDoe". Also, the logon will fail silently, in that after the "signing in" message, no messages or dialogues will show indicating the logon failed. The assumption is that it succeeds but no permissions dialog shows either.
A failed logon from a viewer does say "invalid username or password" as an Address Book Error, but that is a little misleading to the user who may not remember the case sensitivity of their username and think the address book just didn't sync.
If case-sensitivity is by design, more clarity is needed through the documentation and app dialogues to remind users.
My suggestions:
1) Usernames should not be case-sensitive, since typically they are not in Windows.
2) Unsuccessful logons should be prefixed by something more meaningful, eg "RU Server Authorization Failed"
I found when configuring a host to use Custom Server Security, the capitalization of the username matters. For example, logging on with username "johndoe" will fail if the username on the server is "JohnDoe". Also, the logon will fail silently, in that after the "signing in" message, no messages or dialogues will show indicating the logon failed. The assumption is that it succeeds but no permissions dialog shows either.
A failed logon from a viewer does say "invalid username or password" as an Address Book Error, but that is a little misleading to the user who may not remember the case sensitivity of their username and think the address book just didn't sync.
If case-sensitivity is by design, more clarity is needed through the documentation and app dialogues to remind users.
My suggestions:
1) Usernames should not be case-sensitive, since typically they are not in Windows.
2) Unsuccessful logons should be prefixed by something more meaningful, eg "RU Server Authorization Failed"
Conrad,
Support (Posts: 3074)
Jul 17, 2018 8:58:36 am EDT
Hello Marty,
Thank you for your suggestions.
Thank you for your suggestions.
I found when configuring a host to use Custom Server Security, the capitalization of the username matters. For example, logging on with username "johndoe" will fail if the username on the server is "JohnDoe".
Yes, it is by design. We will mention that in the documentation and possibly also in the interface itself. Alternatively, we will consider following the Windows scheme instead.If case-sensitivity is by design, more clarity is needed through the documentation and app dialogues to remind users.
Yes, this is a known issue. We will add a message in case of a failed logon attempt.Unsuccessful logons should be prefixed by something more meaningful, eg "RU Server Authorization Failed"
* Website time zone: America/New_York (UTC -5)