Agentry client password reset

[sravanthi_polu]

Hello Experts,

      Agentry client password that connects to work manager application 5.3 has been reset due to number of failed attempts.But the user cannot login to the application with the new password until and unless the client has been reset.But if a client reset has been done all the unsynchronised data would be lost.Could not identity the reason why the user cannot login with new password with out reset.Agentry client version is 6.0.40.

Please provide inputs.Thanks in Advance.

Thanks & Regards,

Sravanthi Polu

Tags edited by: Michael Appleby

[i834235 · Accepted solution]

You should be able to connect to the Agentry client with new changed password. Even though you see warning client during login but it lets you logon with new password.  Once your  transmit/sync is sucessfull, new password will be  cached locally.  So there is no need to  reset client each time password is set.    Also there are password level settings that can be done in the editor, you may have to check those settings, if they are modified.

Thanks

Manju.

[sravanthi_polu · Accepted solution]

Hi,

      Thanks for the reply, I have tried the scenario by changing Agentry application level security settings(lock out levels), but could not find the solution.

Also tried by changing the password in ECC. But the client is not connecting to server without a reset.

Is it mandatory to reset client when a password is changed in ECC. Please suggest.

Thanks & Regards,

Sravanthi Polu

[bill_froelich · Accepted solution]

Sravanthi,

No, it is not mandatory (nor recommended) to reset a clietn simply due to a password change.  The editor settings are there to help manage your application security settings and will not impact the password change.

When your password changes in SAP, a user who had previously connected via an Agentry client can do one of two things.

1) Login to the client using the old password.  Since it is cached for offline validation the user will be able to login and perform work.  When the user transmits they should be prompted to enter the new password before the transmit will authenticate.

2) Login using the new password.  This will warn the user that the password doesn't match and prompt them to retry or connect to the server.  In this case they would want to select the connect option which will connect to the server to validate the new password and then cache the new one before continuing the transmit.

In either case any pending transactions would still be processed after the new password is validated.

--Bill

[Former Member]

Hello Sravanthi , ya it  should work . but as per my knowledge once client connect to server then password store in local device or folder . so next time until and unless it will not connect to server with new password i think it wont work. still i  will also check more on it . Thanks & Regards, Kunal Varaiya