In oracle we have users with passward expiry date. when the passward expires a message is prompted on screen that passward is about to expire. It is done implicitly by Oracle.
We have developed an web application using Oracle backend for a client. In this application we have created application Users. We have created a Table say users in which we have defined col.
as username,passward, expiry date. when ever user login to application it checks user name/passward and expiry date in users table. if the expirydate is reached a message is prompted that changed the application user passward.
Now the client wants to connect these application users with Oracle users. The requirement is that wheneven Oracle users passward Expiry message appeare on screen the same message will be catched and displayed in application software. Means when Oracle gives warrning about oracle users passward going to expire same message will appear for application software user, and application user and Oracle users passward both needs to be changed.
For this I have suggested to client that we have DBA_Users and user_users view and in that we have Expiry date col.
And add a col. named Ora_expiry_date in ur table where u have stored ur Application username, passward. and update this col. with user_users expiry date col. by this u will have same expire date for Oracle users and Application software user.
But they r not convienced. They want it should be done implecitly in Aplication as it is implecitly done in Oracle. Means when message appears for oracle user the same message will appear for application user.