When activating the setting Only one concurrent login per user under Administration>Settings>Security within the CCM. After saving you enabling this setting and logging out of CCM. When then logging back in you get the following error:
When clicking Ok it takes you back to the login page and does not allow a local or AD user to authenticate to the website after enabling this setting.
What is Expected?
Enabling this setting should just be not allowing multiple logins from the same user on CCM.
How Did You Get This To Happen? (Steps to Reproduce)
Steps are detailed in What You Are Seeing section. Here is a photo of where the setting in question is within the interface:
Workaround
Run the following query to verify that this setting is set to True:
SELECT * from AbpSettings
WHERE Name = 'App.UserManagement.AllowOneConcurrentLoginPerUser'
If it is set to True, run the following query to set it to False:
UPDATE AbpSettings
SET Value = 'False'
WHERE Name = 'App.UserManagement.AllowOneConcurrentLoginPerUser'
Then, in an Administrative PowerShell Session, run the following commands to stop the CCM Website:
What You Are Seeing?
When activating the setting
Only one concurrent login per user
under Administration>Settings>Security within the CCM. After saving you enabling this setting and logging out of CCM. When then logging back in you get the following error:When clicking Ok it takes you back to the login page and does not allow a local or AD user to authenticate to the website after enabling this setting.
What is Expected?
Enabling this setting should just be not allowing multiple logins from the same user on CCM.
How Did You Get This To Happen? (Steps to Reproduce)
Steps are detailed in What You Are Seeing section. Here is a photo of where the setting in question is within the interface:
Workaround
Run the following query to verify that this setting is set to True:
If it is set to True, run the following query to set it to False:
Then, in an Administrative PowerShell Session, run the following commands to stop the CCM Website:
And then the following to start it up again:
And then attempt to login to the CCM website again.
References
┆Issue is synchronized with this Gitlab issue by Unito ┆Milestone: 0.6.3