Business Service Manager 4.7
This is a known issue of Liferay 4.2.2 migrating to 5.2.3.
What happens is previous versions of Liferay uses userId to login. The new version gives the user a choice of using userId, screen name, email address, etc. However, such change has to be done after user login to Liferay. After migration, some users happen to see login screen as userId which is now defined as a long integer Id, not as previously defined as a String name id. So the user cannot login to Liferay using string name id because Liferay expects an integer. And users cannot change login screen option to "screen name" because they are no longer able to login and make changes.
The myMO 4.5 upgrade to 4.7 internally migrates liferay into version 5.2.3.
After migration, before running myMO, run the following script to change the ~mymo/data/hsql contents.
# verify if the hsql data correct or need modificaiton MymoDir=`pwd` #MymoDir="/home/formula" Srcfile="$MymoDir/../data/lportal.script" Destfile="$MymoDir/../data/hsql/lportal.script" if [ ! -f "$Destfile"] then echo $Destfile does not exist, exiting echo please make sure this is run under mymo installation dir exit fi if [ ! -f "$Srcfile"] then echo backing up to $Srcfile mv $Destfile $Srcfile fi sed s/userId/screenName/ $Srcfile > $Destfile echo completed processing $Destfile
After restarting myMO, users can see login screen as "screen name" and thus enter string id to login.