Continuous Portal User Locking

Hi Experts
We are experiencing a problem where the Portal Users are continuously locking themselves when accessing Travel Management.
There doesn't seem to be any valid reason for this and we can't even replicate the problem consistently to try and determine where the problem may lie.
Has anybody else experienced this?
Is there maybe a SAP Note that I can't find which may fix the problem?
Any help and advice will be appreciated, thanks.
Anton

Hi Anton
Our developers corrected the application with OSS note 1466697 for WD ABAP with application of "dirty flag" but there were rendering corrections released for work protect mode - "work protect JS" in the new UR library
1543743
1543744
I'm not WD ABAP expert but I believe this works using wdr_test_portal_workprotect - I searched for similar issue and one other thing to check is the following as otherwise not adhering to following rules can cause issue with locking and navigation.
- Both, the Portal URL and the Web Dynpro ABAP URL need to be URLs with
a fully qualified domain name, ending with a common part of the fully
qualified domain name.
Fully Qualified Domain Names (FQDN): http://help.sap.
com/saphelp_nw70/helpdata/EN/67/be9442572e1231e10000000a1550b0/frameset.
htm
- Web Dynpro ABAP is integrated in a Web Dynpro ABAP iView, and must not
be integrated in a URL iView
Creating Web Dynpro ABAP iViews: http://help.sap.
com/saphelp_nw70/helpdata/EN/1d/e4a34273f60b31e10000000a1550b0/frameset.
htm

Similar Messages

Portal User Locked Hourly ..

Hi,
I have a very strange problem.
Since a password change of the portal user "Administrator", this account is locked hourly.
OS: W2k8
DB: MSSQL 2k8
SAP: Portal 7.00
User: Administrator (UME)
Portal IP: 192.168.1.1
responses.trc
[May 14, 2014 8:42:02 AM ] - 192.168.1.1 : POST /sld/cimom HTTP/1.1 401 1792
[May 14, 2014 8:42:02 AM ] - 192.168.1.1 : POST /sld/cimom HTTP/1.1 401 1792
[May 14, 2014 8:42:03 AM ] - 192.168.1.1 : POST /sld/cimom HTTP/1.1 401 1792
[May 14, 2014 8:42:03 AM ] - 192.168.1.1 : POST /sld/cimom HTTP/1.1 401 1792
[May 14, 2014 9:42:01 AM ] - 192.168.1.1 : POST /sld/cimom HTTP/1.1 401 1792
[May 14, 2014 9:42:01 AM ] - 192.168.1.1 : POST /sld/cimom HTTP/1.1 401 1792
[May 14, 2014 9:42:01 AM ] - 192.168.1.1 : POST /sld/cimom HTTP/1.1 401 1792
[May 14, 2014 9:42:01 AM ] - 192.168.1.1 : POST /sld/cimom HTTP/1.1 401 1792
security.log
#1.5 #00155D11160300650000014F00000F000004F95827B00C09#1400056919503#/System/Security/Audit##com.sap.security.core.util.SecurityAudit#Guest#0#SAP J2EE Engine JTA Transaction : [045ffffffe5ffffff8e00ffffffcefffffffa]#n/a##9d0725f0db4311e3c01800155d111603#SAPEngine_Application_Thread[impl:3]_0##0#0#Warning#1#com.sap.security.core.util.SecurityAudit#Plain###Guest    | USERACCOUNT.MODIFY    | UACC.PRIVATE_DATASOURCE.un:Administrator    |     | SET_ATTRIBUTE: lastfailedlogon=[{0001400053321593} -> {0001400056919450}], SET_ATTRIBUTE: PRINCIPAL_MODIFY_DATE=[{0001400053367448} -> {0001400056919483}], SET_ATTRIBUTE: failedlogonattempts=[{0} -> {1}], SET_ATTRIBUTE: LAST_MODIFIED_BY=[{} -> {Guest}]#
#1.5 #00155D11160300650000015000000F000004F95827B03D0C#1400056919521#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#Guest#0##n/a##9d0725f0db4311e3c01800155d111603#SAPEngine_Application_Thread[impl:3]_0##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.FAILED
User: N/A
Authentication Stack: sap.com/com.sap.lcr*sld
Login Module                                                                                                         Flag        Initialize Login      Commit     Abort      Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT ok          false                 true
2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          exception             true       Authentication did not succeed.
3. com.sap.security.core.server.jaas.CreateTicketLoginModule               OPTIONAL    ok                                true       #
#1.5 #00155D111603006F0000014100000F000004F95827B072ED#1400056919624#/System/Security/Audit##com.sap.security.core.util.SecurityAudit#Guest#0#SAP J2EE Engine JTA Transaction : [045ffffffe5ffffff8e00ffffffcf0]#n/a##9d199c80db4311e38ead00155d111603#SAPEngine_Application_Thread[impl:3]_4##0#0#Warning#1#com.sap.security.core.util.SecurityAudit#Plain###Guest    | USERACCOUNT.MODIFY    | UACC.PRIVATE_DATASOURCE.un:Administrator    |     | SET_ATTRIBUTE: LAST_MODIFIED_BY=[{} -> {Guest}], SET_ATTRIBUTE: PRINCIPAL_MODIFY_DATE=[{0001400056919483} -> {0001400056919606}], SET_ATTRIBUTE: lastfailedlogon=[{0001400056919450} -> {0001400056919576}], SET_ATTRIBUTE: failedlogonattempts=[{1} -> {2}]#
#1.5 #00155D111603006F0000014200000F000004F95827B0B823#1400056919654#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#Guest#0##n/a##9d199c80db4311e38ead00155d111603#SAPEngine_Application_Thread[impl:3]_4##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.FAILED
User: N/A
Authentication Stack: sap.com/com.sap.lcr*sld
Login Module                                                               Flag        Initialize Login      Commit     Abort      Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT ok          false                 true
2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          exception             true       Authentication did not succeed.
3. com.sap.security.core.server.jaas.CreateTicketLoginModule               OPTIONAL    ok                                true       #
#1.5 #00155D111603006A0000019C00000F000004F95827B45A12#1400056920281#/System/Security/Audit##com.sap.security.core.util.SecurityAudit#Guest#0#SAP J2EE Engine JTA Transaction : [045ffffffe5ffffff8e00ffffffcf7]#n/a##9d7ddc90db4311e3b8e200155d111603#SAPEngine_Application_Thread[impl:3]_19##0#0#Warning#1#com.sap.security.core.util.SecurityAudit#Plain###Guest    | USERACCOUNT.MODIFY    | UACC.PRIVATE_DATASOURCE.un:Administrator    |     | SET_ATTRIBUTE: PRINCIPAL_MODIFY_DATE=[{0001400056919606} -> {0001400056920260}], SET_ATTRIBUTE: failedlogonattempts=[{2} -> {3}], SET_ATTRIBUTE: LAST_MODIFIED_BY=[{} -> {Guest}], SET_ATTRIBUTE: lastfailedlogon=[{0001400056919576} -> {0001400056920224}]#
#1.5 #00155D111603006A0000019D00000F000004F95827B463A9#1400056920295#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#Guest#0##n/a##9d7ddc90db4311e3b8e200155d111603#SAPEngine_Application_Thread[impl:3]_19##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.FAILED
User: N/A
Authentication Stack: sap.com/com.sap.lcr*sld
Login Module                                                               Flag        Initialize Login      Commit     Abort      Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT ok          false                 true
2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          exception             true       Authentication did not succeed.
3. com.sap.security.core.server.jaas.CreateTicketLoginModule               OPTIONAL    ok                                true       #
#1.5 #00155D111603005E000000FF00000F000004F95827B4A30A#1400056920413#/System/Security/Audit##com.sap.security.core.util.SecurityAudit#Guest#0#SAP J2EE Engine JTA Transaction : [045ffffffe5ffffff8e00ffffffcfd]#n/a##9d9200d0db4311e3a8cf00155d111603#SAPEngine_Application_Thread[impl:3]_24##0#0#Warning#1#com.sap.security.core.util.SecurityAudit#Plain###Guest    | USERACCOUNT.MODIFY    | UACC.PRIVATE_DATASOURCE.un:Administrator    |     | SET_ATTRIBUTE: lastfailedlogon=[{0001400056920224} -> {0001400056920362}], SET_ATTRIBUTE: LAST_MODIFIED_BY=[{} -> {Guest}], SET_ATTRIBUTE: failedlogonattempts=[{3} -> {4}], SET_ATTRIBUTE: PRINCIPAL_MODIFY_DATE=[{0001400056920260} -> {0001400056920395}]#
#1.5 #00155D111603005E0000010000000F000004F95827B4AB21#1400056920424#/System/Security/Authentication##com.sap.engine.services.security.authentication.logincontext#Guest#0##n/a##9d9200d0db4311e3a8cf00155d111603#SAPEngine_Application_Thread[impl:3]_24##0#0#Info#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.FAILED
User: N/A
Authentication Stack: sap.com/com.sap.lcr*sld
Login Module                                                               Flag        Initialize Login      Commit     Abort      Details
1. com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT ok          false                 true
2. com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          exception             true       Authentication did not succeed.
3. com.sap.security.core.server.jaas.CreateTicketLoginModule               OPTIONAL    ok                                true       #
Normaly that means that the CIM Client is not correctly configured, but the SLD runs over the SolMan (7.1) and in the VisualAdmin > Server > Services > SLD Data Supplier
HTTP Settings and CIM Client Settings are set to the SolMan host and uses the SLDDSUSER to sync the data with the SLD.
Does anyone have an idea what process will connect hourly to the portal where the Administrator is set as user?
I've been searching and reading the now for over two days on the SCN and the web, but I didn't figured it out.
It looks like the portal itselfs want to connect to the local /sld/cimom but the SLD of the portal is still stopped, and also if its running, I get the same error every hour.
Thanks for any advise!
Tobias

Hi Tobias,
Please do the following once, if possible.
1. Please change the password of administrator user and save the password in secure store and recycle the system.
2. You may create a user with equivalent access/permission like administrator temporarily, until this problem is resolved, so that you can unlock the administrator logging in with that id.
3. Please check if that administrator is being used in any connection from java stack, where the password is still old.
4. Attach the default trace here at the time when the user is getting locked. We want to check further.
5. You can follow what David advised in the SAP note, if you can identify the real cause, otherwise follow the above steps.
Thanks.
Regards,
Sujit Kumar Banerjee.

WAS Portal User locked - Due to bad logon

Hi,
Is it possible to adjust user's bad logon attemp in WAS portal 6.4?
If a user enter wrong password more than three time, the system locked that user. It happened three times to admin user. We activated SAP* and unlocked the user.
If any one knows like how to increase the number of wrong password attempt...it would be great.
Thanks,

Hi,
For increasing the logon attempts, you have to follow below steps:
Step 1: Go to <Driver>:\usr\sap\<System ID>\JCxx\j2ee\configtool --> Configtool.bat
ex: C:\usr\sap\Y76\JC03\j2ee\configtool --> Configtool.bat
Step 2: cluster-data --> Global server configuration --> services --> com.sap.security.core.ume.service
select property : "ume.logon.security_policy.lock_after_invalid_attempts = < Enter Number>"
ex: ume.logon.security_policy.lock_after_invalid_attempts = 6
Step 3: save
Step 4: Restart the Engine.

Portal User Locked

Hi Paul,
I have the same problem as reported by Vikas. I have a user called "test2" who is locked out due to login failures.
When I click on the link you have provided to get more info, I get the "Server not found" message. Could you please forward me the information ?
Thanks
-Virinder.

Hi Paul,
Thanks for the input. I ran the ssounlck.sql script but I cannot still login. I get the message "Your username has been locked out from this IP address".
Here are my settings from Login Server's Account Lock Policy:
Global lockout duration: 1 days
Lockout duration for one IP address: 15 mins
Single Sign-On session duration: 24 hrs
Do I have to change these settings to see the unlocking taking place today ? Also, what if I want the Global lockout duration to be less than 1 day ?
Thanks for your help,
-Virinder.

Sync User Locks from LDAP(Microsoft AD) to Portal UME

Hi All,
Currently we have our Portal UME connected to LDAP (Microsoft AD) as our data source. I can bring up all Active Directory users in Portal, however the users that are locked and disabled in Active directory are still active in portal. To be more clear the expiration date of a userid in AD does not sync with Portal UME account expiration date. Is there a way to bring in the expiration value in to portal?
Regards,
Junaid

Config tool may not have expiry date as mapping in Additional LDAP prop tab, you may need to look for configuration file where you can map the logical attribute to the LDAP.
Licensing impact depends on your contract with SAP.
However you can check portal users with USMM at the end of URL.
E.g.
remove 'irj/portal' from your initial portal link and add 'usmm'

If user locked (backend) then from portal i m not able to send data

If user locked (backend) then from portal i m not able to send data
both user are same in front end and backend.
But once user is unlocked i am able to send data from portal to backend...
Regards
Ruturaj

Hi
Since you are in CUA landscape(as u said portal and r3 user are same) unless and utill you unlock it data will not be process.
[Help|What's the right user to access;
BR
Satish Kumar

Method of fetching Account status and user locked date in Portal.

Hi,
Can anyone suggest me the method name in UME API in Sap Ep for fetching User Account Status and Last User Locked Date. Or suggest a related code for it.
user database is LDAP.
Thanks

Hi Abhai,
The class (actually Interface) you're looking for is IUserAccount. You can get this from the IUser by using the method getUserAccounts().
The IUserAccount provides all sort of methods like lockDate(), isLocked(), getLockReason().
See more in https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sapportals.km.docs/library/ep/_d-f/ep%206.0%20sp2%20usermanagement%20public%20api
Best regards,
Amit

Users locks during portal application

There are two back buttons on the portal application
- one on the transaction
- one in the top right corner of the screen.
When the user is in the middle of a transaction and uses the back button located on the transaction level to back out of the transaction, any locks in SAP are correctly backed out; however, if they use the Back button located in top right of the portal screen, the users locks up within SAP. Whenever this locking occurs, the only way we have found to get through it is to have their SAP sessions manually killed or they have to wait 30 minutes for the transaction to release in SAP - obviously, neither of these are acceptable solutions.
I'm hoping that there is a setting that we can use to force a cancel of the transaction in SAP when the user performs either of these scenarios.
Can anyone propose a solution to address this issue?

Hi,
Pls check in the system Admin->Monitoring I think we can find in this.
Or try to check in User Admin->Keystore admin
Regards
Lekha

Can I use SAP HR to drive ESS Portal user creation?

Hello
We are implementing a new instance of SAP HR and Portal for ESS and MSS and I am not sure of all the steps that need to be completed so any guidance / tips would be greatly appreciated.
Company currently has an LDAP - but not used extensively. Not all employees currently in LDAP as not all have network ids. All employees will have a SAP account to enable ESS (via Kiosks etc). ESS iViews in Portal will call SAP HR and possibly SAP BW. We have an instance of SAP already and user admin maintained via CUA - this will continue.
Scenario:
My initial thoughts are that we try to use SAP HR as the leading system to drive the ESS Portal users and access. Basically I want to create the user in SAP and assign them an ESS SAP role... then through syncronization have the user created in the Portal and have the correct ESS Portal assigned (in the Portal)
My thinking so far is to go the following way;
1) Create User Master Record in SAP (SU01)
2) Hire employee into the org structure (via HR processes)
3) Populate Infotype 0105 with SAP username
4) Populate Infortype 1016 - with SAP role to be assigned to allow ESS access (not sure about this aspect) or role could be assigned in 1) above
I am not sure of the next steps - I think there must be a way in an SAP table to map the ESS SAP role to the ESS Portal Role (is this via WP3R?)
then I am hoping that a standard job can be run (is this RSLDAPSYNC_USER) that will create the user in the Portal (UME?) and assign the correct Portal role ?
(obviously configuration needed)
For MSS and HR Power users - we would continue to assign SAP roles via SU01.
Can anyone assist with;
- Is my thinking correct in terms of how this should / could work?
- in SAP how can I map SAP Roles to Portal Roles ?
- will syncronization in SAP create the user in Portal and assign the role ? what do I need to configure?
Thanks in advance

Dear Michale,
I just dont know if this can throw some light on your prob.'
In our Orgn we had around 250 ess users and 200 sapr/3 users. Some of the r/3 users also logon to ess via their r/3 uname and password.
What we have done is like follows:
1. Created a role for only the ess users ZHRESS. For this i asked the HR functional people with sap_all profile to do all the job which the ESS users are supposed to do and tracer the authorization via tcode st01. We created the role on the basis of this trace report.
2. For the purely ESS users we created the users via tcode HRUSER and assigned then with the above role.
3. For the R/3 users who are supposed to avail the ess facility we assigned them with the role ZHRESS role in addition to the other roles assigned to them to carry out their normal R/3 transactions. Then we mapped their R/3 uname to their employee no via PA30 infotype 105.
4. Tcode HRUSER saved time which would have consumed had we done it via su01 and moreover it picked Name etc data from the HR master table. In HRUSER tcode , setting the user attributes helps to define what roles the users are to be assigned, what should be their initial password etc.
Pl let me know if it satisfies you querry.
Regards

Redirect portal users to accept "terms & conditions" ...

Here is the requirement ..
When the users logging in first time i need them redirected to a page to accept "terms and conditions" , next time the page should not be appeared.
Only the "terms and conditions" page should be appeared for those who are not accepted before.
Please help me if anyone knows the solution ...
Thanks in advance
MMK

Hello Eric, First off I'm very new to SAP, I've been a Basis Admin now for about 6 months... I have had the pleasure of joining a team at the beginning of an upgrade.
An issue Iu2019m trying to resolve is a payroll issue. Apparently in 4.7 when a user would login to the portal and view their personal data it would not u201CLocku201D their user data.
But this appears not to be true in ECC6/Netweaver 7.0. When our HR does payroll, if a user is logged in to the portal, and viewing their personal data the u201CPayroll Runu201D will not complete.
So what I would like to do is implement your solution for the Redirect portal user to the u201CTerms & Conditionsu201D page, and tweak-it to forward the users to a u201CWebsite is downu201D page.
Here is my thinking. When a user logs-in, check either a z-table or some other table that holds some value. If the value is True then do nothing and continue. If the value is False, then Re-direct the user to a u201CWebsite Downu201D page with just an OK button, that when clicked will call the Logoff function.
Also HR would be able to run a job that would set the value to either True or False so they would be able to take the portal u201COff Lineu201D when they choose..
My question isu2026 Can you give me detailed information on how to accomplish this?
Thanks
Steve

How to force logout of portal user

Hi all,
we're currently facing trouble with portal users being "locked" in the portal. They are not locked in the ume sense, but when trying to logon they are only able to see navigation framework, and no content. The only content we're using in the portal is MSS/ESS, so the content we're trying to load is from R/3.
My idea is to manually log out the user in trubble from the portal.
Now; I can see see active http_sessions using the telnet Administrator session, but I can't find a way to force logout a user. Can anyone please tell me how to?
We're using Portal SP11, and ESS/MSS SP7.
I'm thankful for all input! Points will be handed out of course.
Kind regards,
Andreas

hi,
Try this code.This might help you.
IPortalComponentRequest request=(IPortalComponentRequest) this.getRequest();
IAuthentication Authen = UMFactory.getAuthenticator();
HttpServletRequest req = request.getServletRequest();
HttpServletResponse res = request.getServletResponse(true);
//logoff user from Portal
Authen.forceLogoffUser(req, res,"");
The third argument is a string which is the redirection URL.
Regards,
Srinath

Fetching Currently Logged in Portal User & Fetch Users logged on whole day

Hi All,
I want to fetch the Currently online Portal Users and their name.
Also we want to fetch all users from different servers as we have load balancing.
Also i want to fetch which users have logged on a particular day, so that i can come to know that at end of day which users have logged on.
Thanks & Regards,
Dhruv Shah

Hi,
you can connect to the above mentioned tables by creating a alias or else using the default alias
for this you have to login into the visual admin
server ---> services -
> jdbc connector
there you can find the table with the alias.
The default aliases what i know are SAP/BC_JMS,SAP/BC_UME,SAP/BC_WDRR.
I think this will be usefull
or else craete a new alias using Add alias button.
The code for getting connection is
      InitialContext ctx = new InitialContext();
      DataSource ds = (DataSource)ctx.lookup("jdbc/SAP/BC_JMS");
     Connection con = ds.getConnection();
//you can write ur select statement and continue
But i have a doubt can you tell me what information does these tables contain.
Thanks & Regards,
Lokesh
Edited by: lokesh kamana on Aug 26, 2008 8:57 AM

Sound pausing shortly when user locks iOS device?

Hi,
The bug causing a background sound to stop, when a user locks the screen on iOS device, has been lately fixed in AIR 4.0 beta.
However, now with beta 4.0.0.1390, when the device is locked or goes into sleep mode, the sound stops for 2 seconds (sometimes a bit more, it depends on the device power), then the sound continues playing. It happens on various devices (iPhone 3GS, iPod 4 and iPhone 4S) and multiple OS (5.1.1, 6.0.1, and 7).
My code is very simple, and uses the standard Sound.play() function. Of course it is better than the previous behaviour, since at least now the sounds continues after a while, but this cut can get annoying. Before I submit a bug, do you guys encounter the same issue?
Thank you!
Frédéric

Hi Nimit,
Thank you for validating this issue. I created a bug report here: https://bugbase.adobe.com/index.cfm?event=bug&id=3692617
Since I am creating an audio app, this one is critical for me.
Good luck!
Frédéric

WF-BTACH user locked in the Producation

Hi Experts,
In producation, wf-batch user locked due to some reasons for two days. Now we unlocked the user and all workflow's are working fine.
But the problem is, there are some 200 workflow's are triggered on the same two days. Most of those workflow's are hanged. All the background tasks in workflow's are having the status as 'Ready'.
We are not able fix this using transaction SWPR - continue workflow after error and SWPC. Because those are workflow's are listed in the above transaction.
Is there any way to restart those workflow's? there is no error in the workflow. Its just hanging in the middle.
Kindly help me on this.
Helps will be highly appreciated.
Thanks,
Nandini.

Hello Nandini !
You have stated that background tasks are in "READY" state.Check in the workflow log whether all the parameters are populated properly for those background tasks.If not, check any exceptions are thrown.The exception message should state why the background task is not in "COMPLETED" status.
Ensure why container values are not populated for those background tasks and enter the appropriate values to those containers in workflow log and execute the workflow from SWPR.
Regards,
S.Suresh

Unlock portal users

hello,
did anyone try to write a webservice to unlock portal users ?
I'll explain my situation:
I want to add a button or a link in the loggon page (sap netweaver portal) . This should call a webservice that will unlock the user who locked himself by passing wrong passwords too many times.
Let's not be worried about the sap system behind. All I am interested in is the sap netweaver portal.
How can we do that?
pleaasse help !!

Hi Kranthi/Jhansi,
Thanks for your response, am able to resolve the issue. I've awarded the points.
Guys, here's the correct code for future reference.
Layout: An input field for user ID and a button
Context: Attribute -> UserID type string for UserID bind to the input field
Code: In Action Method of button, wrote the following code:
import com.sap.security.api.IUserAccount;
import com.sap.security.api.IUserAccountFactory;
import com.sap.security.api.UMException;
import com.sap.security.api.UMFactory;
public void onActionulock(com.sap.tc.webdynpro.progmodel.api.IWDCustomEvent wdEvent )
    //@@begin onActionulock(ServerEvent)
    IWDMessageManager msgMgr = wdComponentAPI.getMessageManager();
    IUserAccountFactory accntFactory = UMFactory.getUserAccountFactory();
    try {
          IUserAccount accnt = accntFactory.getUserAccountByLogonId(wdContext.currentContextElement().getUserID());
          IUserAccount mAccnt = accntFactory.getMutableUserAccount(accnt.getUniqueID());
          if (mAccnt.isPasswordLocked())
               mAccnt.setLocked(false, IUserAccount.LOCKED_BY_ADMIN);
               mAccnt.save();
               mAccnt.commit();
               msgMgr.reportSuccess("ID Unlocked Successfully");
          }else{
               msgMgr.reportException("ID not locked",false);
     } catch (UMException e) {
          msgMgr.reportException(e.getMessage(), false);
    //@@end

Continuous Portal User Locking

Similar Messages

Maybe you are looking for