| Forms raise frm-41352 when password expired [message #466715] |
Tue, 20 July 2010 13:57  |
Kaeluan
Messages: 179
Registered: May 2005
Location: Montreal, Quebec
|
Senior Member |
|
|
Hi,
we are working to increase the security of our oracle application by adding profil and expiration to all our database username.
Expiration is actually set to 60 days.
So if i understand it correctly, 60 days is counting from when i change my password. So if I change it at 10:30am it will expire at 10:30am in 60 days.
Our forms application is calling all forms using the command open_form with SESSION parameter to open all forms in new session.
My problem is when the user connect in the system let say at 9:00am. At 10h30am the password will expire and when the user will click to open a new form from the application he will get the message ORA-28001:the password has expired.
The new module will open even if password is expired and will raise the error FRM-41352: Failed to create session. So the module will stay in the same session than the caller.
Is there a way to catch the ORA-28001 and force a new logon.
Probably with some code in the ON-ERROR of the called module but this mean that i will have to change +400 forms. Any other way ??
Regards,
|
|
|
|
| Re: Forms raise frm-41352 when password expired [message #466784 is a reply to message #466715] |
Wed, 21 July 2010 02:46  |
 |
djmartin
Messages: 10181
Registered: March 2005
Location: Surges Bay TAS Australia
|
Senior Member
Account Moderator |
|
|
Can you set a 'grace' period ( of say 5 days) so that the user is given a message to change their password and then you modify only the 'splash' screen to test for full expiry or to say that they are in the 'grace' period and assist them to change their password?
David
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
