This content has been marked as final. Show 6 replies
How is your authentication defined - as "Custom" ?
With a function like APPS.FND_WEB_SEC.validate_login available to you, I would leave page 101 alone and provide ebs_authenticate as your "authentication function name" using custom authentication scheme type.
blog: [url grassroots-oracle.com]grassroots-oracle.com
twitter: [url twitter.com/swesley_perth]@swesley_perth
-- please mark any useful posts as helpful or correct, in the end it helps us all
Thank for your quick reply.
I created the custom authentication and in Authentication Function Name field i given my function name ebs_authenticate
Perhaps your answer may be found here:
FND_WEB_SEC.Validate_Login not working
It could be security regarding the use of fnd_web_sec.
You could also capture the result of apps.fnd_message.get to determine why the authentication fails.
Thanks for your help, its working fine.
Just be wary that when using that API, all you are doing is validating against the username and password - it doesn't store any audit record, update the last login date etc on fnd_user. This might not be a problem for you however if you have a user just using APEX from EBS (as we did) then any monitoring scripts can make it look as though the account is not being used.
There is an internal API (in fnd_user_pkg I think) which does this, but obviously it's up to you whether you want to risk using that (because it's unsupported).
This might also be worth a read