This is a known issue that is under investigation. The issue is where the login URL gets corrupted in the DB.
Workaround:
On a cmd line, follow these steps to clean up the corrupted login URL from the DB.
Source the environment using oware for windows or . /etc/.dsienv for Linux
SELECT * FROM lportal.Layout WHERE friendlyURL LIKE '%login%';
Shutdown Web Server
cmd> oware or . /etc/.dsienv
cmd> mysql -uroot -pdorado
Verify you have an issue with login
sql command> SELECT * FROM lportal.Layout WHERE friendlyURL LIKE '%login%';
If yo u have
sql> update lportal.Layout set typeSettings ='layout-template-id=1_column\ncolumn-1=58,\n'where (groupId=10180)AND(privateLayout=0)AND(friendlyURL='/login');
sql> update lportal.layout SET friendlyURL = '/login' WHERE friendlyURL = '/login-/login';
Start the Web Server
If Successful please update your case for authorization to close.
If clearing out the corrupted URL command doesn't work, please send the following output to Dorado Support: tsc@doradosupport.com
Source the environment using oware for windows or . /etc/.dsienv for Linux
cmd> oware or . /etc/.dsienv
cmd> mysql -uroot -pdorado
SELECT * FROM lportal.layout WHERE friendlyURL LIKE '%login%';
update lportal.Layout set typeSettings ='layout-template-id=1_column\ncolumn-1=58,\n'where (groupId=10180)AND(privateLayout=0)AND(friendlyURL='/login');
Author: tv