Access management problem i V15 
Autor: Thomas MurrayIn V13, the user was identified with the Username in the Access Management page. Members of a club can share the Username and Password to access the protected pages. A smaller group can use a different Username/Password to access more protected areas. The members of these groups do not share a common E-mail Address that can be used as a common identifyer.
In V15 however, the user must have a correct E-mail Address as identifier. Any attempt to enter a new user that has no E-mail Address fails.
In my case this means, that I had to abandon the V13 to V15 upgrade and go back to V13.
Is there any plan to correct this mistake so an V13 to V15 upgrade will be possible?
This problem means that I will have to stick to V13 in order to have suitable format of the usernames. The problem should be very easily solved if both formats are allowed. It should be up to the administrator to select the usernames that best serves the application.
Thomas Murray
Autor
The problem seems to be solved in Version 15.2.2
Autor
Unfortunately, I was to quick to declare the problem solved. The "User name" field when logging in on the "Reserved Access" page in V13 has been replaced by an "E-mail" field in V15. Because of this problem, I have been forced to go back to V13 with my application.
There is one very simple and obvious solution to this problem, and that is to let the administrator decide which of the two formats to use.
What is the reason for causing this quite unnecessary problem?
Is there no chance that it will ever be fixed?
I maintain a website for a club. They simply all login with member at rotaryclub.com and a common password, it works just like a username. I preferred username, but email address works and will make my life easier if they ever choose to restrict access to individuals.
Autor
Thanks för your reply.
The possibility to use an e-mail address as identifier is quite useful for logging in to an account at e.g. Outlook, Google or WebSite where each individual has to be treated as a separate account.
In the present case, however, a group of individuals shares a username/password combination. They do not have any common e-mail address to be used as an identifyer. This disadvantage in V16 by far overides any advantages over V13 in the present application.
For me, it is quite impossible to understand why this problem needs to exist at all. If the administrator could choose one of the two options depending on the actual needs there had been no problem!
Until this problem is solved, I will have to stick to V13.
Thomas, as I stated, I simply created a dummy email address and gave it a password. Everyone is still happy (eg me at mydomain.com)
Autor
As I mentioned, V13 works fine the way I want.
What is the point for me to update to a new version that does not?
Why is the problem not fixed in the current version so both username and e-mail work as identifier?
Hi Thomas.
As of now, this matter will not be trated as a bug, since it is the current expected behavior of the login function.
It is absolutely understandable though, that there might exist cases where an username might be mandatory, such as this one.
For this reason, I would like to ask you to open an IDEA topic about it, explaining the situation (if you still did not do that), so that it can be highlighted better for the staff to discuss later on.
I would like to thank you for your understanding and I apologize for the concerns this change might have brought
Stefano
Autor
Hi Stefano
As far as I understand I opened this conversation as an Idea topic, Posted on the 04/27/2018 15:19:46. My first entry in that conversation has a bulb to indicate just that.
Thomas
Autor
Hi again
I have now tried Website X5 Ev V16.1.1 as an administrator with all the administrators rights.
Running the app logged in as an administrator it works fine and the problem discussed above seems to be solved.
When running Website X5 V16.1.1 as an ordinary user, however, with its sligtly redused acess possibilities, I have to enter the administrators password and all the website activation codes each time I start the application.
So I will have to stick to V13 until that problem is solved. V13 does not have any problems when run as an ordinary user.
Thomas
Autor
There is the sam problem with V16.2.1.
Thomas