asked on

UserID locked or expired for the application on Websphere

Hi,

I have installed an application on Websphere Application Server v6.1. I have enabled the global security and the application security through Admin console and we are using the Standalone Custom registry.

After 2 months when I try to access the application I am getting an error like

"Your password has expired or you have exceeded the number of login attempts allowed by your administrator.
Your password must be reset. Inform your supervisor. "

Now I am able to access the websphere admin console with the same userID and password but its not working for the application.

I have checked in the DB2 database too where the userids stores for that application, but I coudn't find the parameter called active or inactive for that userid.

Can anyone please help me how I can reset the password for the application installed on websphere.

Thanks,
WASAdmin

HonorGod

That sounds like it would be some password validation within the application, not in WebSphere.

Could you uninstall, and reinstall the application?

That might let you set up the userid and password for the application.

WASAdmin25

ASKER

Yes, I can reinstall the application. But thats the last option I will prefer.

Is there any other way we can unlock the password for the application???

HonorGod

Let me try and find out... I'll get back to you shortly.

HonorGod

Can you use the administration console to make configuration changes?

WASAdmin25

ASKER

Yes, I can use the Amin Console for any config changes.

I tried to disable the global security and the application security from the Admin Console and restarted the Dmgr, Node and the App server.

But, still when I try to access the application I am getting an exception like I mentioned earlier

"Your password has expired or you have exceeded the number of login attempts allowed by your administrator.
Your password must be reset. Inform your supervisor. "

is there anything I can make changes to the configuration in websphere???

HonorGod

That's what I'm trying to check

HonorGod

ok, it sounds like your LDAP server has some expiry date for the particular user in question.

There is a tool/utility that is attached to this IBM WebSphere technote called LDAPsearch. Here is a technote that explains how to use the tool to diagnose these kinds of issues:

http://www.IBM.com/support/docview.wss?rs=180&uid=swg21113384

It can be used to verify, what is happening for a specific userid / password combination on the LDAP server.

I'm guessing that the userid has "expired", as far as the LDAP server is concerned, so when attempts are made to authenticate this user, the LDAP server is returning an indication of the situation, and WebSphere is causing the message seen above to be displayed.

WASAdmin25

ASKER

Actually we are not using LDAP registry here but we are using Standalone Custom registry.

Any idea how to deal with Standalone Custom registry???

HonorGod

What kind of "Custom" registry?

And, most importantly, (exactly) what version of WebSphere is being used?

To determine this:
- open a command prompt
- "cd" to the <WAS_HOME>\bin directory
e.g., cd C:\IBM\WebSphere\AppServer\bin
- Use the versionInfo command script to display the product version details
on Windows:
> versionInfo
on Unix type systems:
# ./versionInfo.sh

and paste the version details here.

Thanks

WASAdmin25

ASKER

In the Admin Console when we go to Security --> Secure administration, applications and Infrasturcture--->

at the bottom of the page we will find four options under user account repository

i.e 1. federated Repositories
2. Local Operating System
3. Standalone LDAP registry
4. Standalone Custom registry

Here I have selected the fourth option i.e Standalone Custom registry and we specified the Custom registry class name as "com._360commerce.commerceservices.security.websphere.COUserRegistry"

The version we are using here is WAS V6.1.0.17 in Windows 2003

Please let me know if you need any additional info.

HonorGod

So, from where did you get the

com._360commerce.commerceservices.security.websphere.COUserRegistry

code?

HonorGod

FYI: The "latest" release of that version of WebSphere is 6.1.023, dated 23 March 2009.

I would encourage you to upgrade to it.

To find how:
- Browse to the WebSphere Application Server support site
http://www.IBM.com/software/webservers/appserv/was/support/
- Click on the "Download" link the the "blue" section to the right of center
- Click on the "Recommended fixes" link
- Click on the "Version 6.1" link, which will display the "Version 6.1" table
- Scroll down to the section headed with "Other V6.1 tools and fixes", and
locate the row with "V7.0 Update Installer"
- If your version of the UpdateInstaller program is down level, upgrade it
first, then use it to install the 6.1.0.23 release of the AppServer product.

WASAdmin25

ASKER

Thanks for your response !!!

But here as per the configuration settings we are prompted to use the version V6.1.0.17

I don't think thats the version issue because the same application is working fine in other environments with the same WAS version.

The only reason its working is because the application is being actively used in the other environments.

So, I would like to know is there any other configuration changes to be done to the application on the Websphere side.

Please Advice !!!!

WASAdmin25

ASKER

Regarding your previous question

So, from where did you get the

com._360commerce.commerceservices.security.websphere.COUserRegistry

code?

Ans: Its been developed by the Java developers and we got this registry class from the customer.

It came with the application source code ..

ASKER CERTIFIED SOLUTION

HonorGod

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

WASAdmin25

ASKER

I figured out the problem....

I have updated the table in the Database where the userids are stored.

I mean I have updated the column in the table with the current time stamp and restarted the App Server and the Database.

It worked !!!!

Now I am able to login to that application ....

Thanks for help....

HonorGod

You are very welcome. I'm glad that you figured it out, and also happy to hear that you were willing to share the specific details with the rest of us.

Is there anything else?

WASAdmin25

ASKER

I think I don't have any questions right now....

Thanks for asking though........

WASAdmin25

ASKER

issue is resolved

HonorGod

Just curious, why #a24081130 wasn't the solution?

It clearly states:

This user registry is not part of WebSphere...

HonorGod

Thank you for the grade & points. You just made me the 1st WebSphere Wizard!

Good luck & have a great day