Some Account Contact users may be unable to log into UMP 8.4 from certain browsers while they are successfully able to log in from other browsers.
Account Contact users from a single account may be able to log in successfully while contacts from other accounts may not be able to log in from the same web browser.
UIM/LDAPusers who are not associated with an account will be unaffected.
In the portal.log (located in the same folder as the wasp probe log), the following error will be seen when the user attempts to log in:
12 May 2016 16:47:36,483 ERROR [NmsAuth:405] Login failed for Account/username: javax.security.auth.login.FailedLoginException: login failed
Where "username" is the username of the user who is attempting to log in, and "Account" is NOT that user's account, but another account on the system.
Users from the account listed in the error message will still be able to log in.
1. stop wasp
2. edit the file \wasp\webapps\ROOT\WEB-INF\classes\portal-ext.properties
3. Locate the following line:
login.events.post=com.liferay.portal.events.ChannelLoginPostAction,com.liferay.portal.events.DefaultLandingPageAction,com.liferay.portal.events.LoginPostAction,com.firehunter.ump.auth.LoginAction
Just below this line, add the following line:
logout.events.post=com.liferay.portal.events.LogoutPostAction,com.liferay.portal.events.DefaultLogoutPageAction,com.liferay.portal.events.SiteMinderLogoutAction,com.firehunter.ump.auth.LogoutAction
4. activate wasp
You may need to clear the browser cache and cookies but after this the issue will be fully resolved.