|
| Hi all,
I have a problem regarding logon to the portal for users with special characters. For the users in my firm with usernames with special Norwegian characters, such as æ, ø and å, there are problems with logon. These problems occur most of the time, but not
always, perhaps 60% of the login requests fir these users fail. The users are redirected back to the logon page, no errormessage is displayed. Once it happens, the users are not able to log back on for some time, no matter how many times they try. I also
discovered the following:
· If the portal is restarted, all users are always able to log on to the portal
· If I alter the access rights to some of the pages on the portal, all users are always able to log on to the portal
From this I suspected this had something to do with caching of the user credentials. What I did was to reduce the cache timeout on the General secutity tab in WAS to the minimum of 30 seconds. This resulted in that when the users get logged out, they only
have to wait a maximum of 30 seconds before a new login will succeed. The problem is that users with special characters are logged out very rapidly. It?s of course very annoying having to enter username and password every time you have been inactive for
a minute in the portal, but it?s better than not having access at all. Users with no special characters are not experiencing these problems.
The users are authenticated with LDAP correctly, cause if they enter an invalid password, the ?Invalid username/password? is displayed. We use AD as LDAP.
In the logs, the following error message is displayed every time the users gets redirected back to the login page:
?JaasLoginHelp A SECJ0222E: An unexpected exception occurred when trying to create a LoginContext. The LoginModule alias is system.WEB_INBOUND and the exception is com.ibm.websphere.security.auth.WSLoginFailedException: SecurityName is null.? This is no
t a cookie accepting issue as some of the posts regarding this issue suggests.
I also added tracing on the puma packages in WPS to see if this could give me a clue on what went wrong. I added the following trace string:
com.ibm.wps.puma.*=all:
com.ibm.wps.sso.*=all:
com.ibm.wps.services.authentication.*=all
I tried to see if the log result of a successful login attempt differs from the unsuccessful one. As far as I could see, they were pretty much the same.
Version of the various components:
WAS 6.0.2.7
WPS WPS 5.1.2
Active Directory as LDAP
Any help would be greatly appreciated! Let me know if anything is unclear or more information is needed, thanx!
Marius
|
|