Q:
iseries Client Access does not allow third parties applications to open the login screen to change password when it's expired.
Hello all:
I will apreciate any help about this problem.
I am a system administrator (mainly Active Directory) now dealing with this ISeries Client Access Problem in my 400 workstations.
There are e few applications in the company, developed in FoxPro and Visual Basic, accesing the AS/400 (now a new 810) throwh ODBC.
With older versions of client acccess -NT/95 and Express- those applications' login screens work fine if the user password was expired. A pop up window comes out and let the ens-user to change his/her password by himself.
Now, using ISeries Client Access, that does not happens and the end-user then disable the account trying to login more than 3 times.
This is a pain. Only Iseries interfaces activate the native Login Screen. WHY????
Is that a security measure??? Again, WHY???
I am looking for workarounds to solve this problem beacuse the developers are not very familiar with Iseries client access API's (me neither) and I don't beleive we'll need to re-design the login function for all our applications.
Again, any comments, suggestions, etc., will be appertiated.
Roman Gomez
I will apreciate any help about this problem.
I am a system administrator (mainly Active Directory) now dealing with this ISeries Client Access Problem in my 400 workstations.
There are e few applications in the company, developed in FoxPro and Visual Basic, accesing the AS/400 (now a new 810) throwh ODBC.
With older versions of client acccess -NT/95 and Express- those applications' login screens work fine if the user password was expired. A pop up window comes out and let the ens-user to change his/her password by himself.
Now, using ISeries Client Access, that does not happens and the end-user then disable the account trying to login more than 3 times.
This is a pain. Only Iseries interfaces activate the native Login Screen. WHY????
Is that a security measure??? Again, WHY???
I am looking for workarounds to solve this problem beacuse the developers are not very familiar with Iseries client access API's (me neither) and I don't beleive we'll need to re-design the login function for all our applications.
Again, any comments, suggestions, etc., will be appertiated.
Roman Gomez
ASKED:
Feb 28 2005 7:41 PM GMT
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
A:
RATE THIS ANSWER
0
Click to Vote:
0
Click to Vote:
- 0
0
========================================================================
Only Iseries interfaces activate the native Login Screen. WHY????
Because your other software hasn't been updated to current standards. The interfaces are published and available from IBM. It can't be considered IBM's responsibility to keep some other vendor's software up to date.
Tom
