Why do you need to build a custom user authentication process? What's the business requirement?
as i have describe in my question , we need to send the user right after a successful authentication to our own custom form page where he will need to fill some data. After the submission of those data we will save them in our database and then we will redirect him to the dashboard. In simple words every user must fill some data right after a successful authentication and unless he fill that particular form he should not be allowed to view any user page.
You are describing a process - what is the business requirement to do so ?
The authentication process through EBS page is complicated and adding more page(s) between the login process and the user main page is not supported.
One suggestion is to have a different login process for the first page (EBS not to be involved here) and redirect those users who fill that particular form to EBS login page, others won't get access to that page.
And we are still waiting for the business requirement -- Why this custom form has to be added after you login and before seeing the user main page? What does it contain? Are you trying to enforce something here?
We need to add two or three factors authentication in order to make a stronger authentication sequence. Every time when user will logged into the system he will receive a pincode on his device , so the user must enter this code on the custom page form and based on this pin code he will be allowed to access the entire dashboard etc. So the business requirement is to provide more than one factor authentication...hope this will explain
For stronger authentication process, Oracle provides password security that can me implemented.
How To Setup Password Security? (Doc ID 564125.1)
R12: How To Force Users To Use A ‘New Password Strategy’ ? (Doc ID 1643115.1)
Oracle also provides methods of tracking changes done on EBS (Sign-on audit and Audit Trail).
How To Track Changes Done On Oracle E-Business Suite (Doc ID 1262586.1)
How To Audit An Oracle Applications User? (Doc ID 395849.1)
Auditing: How Do I Audit Responsibilities and Data? (Doc ID 436316.1)
Overview of Audit Trails in Oracle Applications (Doc ID 60828.1)
Understanding Data Auditing in Oracle Applications Tables using Audit Trail (AuditTrail) (Doc ID 69660.1)
Another option would be using SSO -- Overview of Single Sign-On Integration Options for Oracle E-Business Suite (Doc ID 1388152.1)
If the above still doesn't meet your business requirements then you may need to implement what was suggested in my previous reply, you can implement as many factors of authentication you want before you reach the main EBS login page without interfering with the main login page process.