I have created forms in webdb as user1. Created a web site as user1 under schema one. Have created contexts that restrict access to data in forms(only want users to see their own data). Have some forms that public may see. Others only signed on user can see. DADs of one and ones were created. Webdb points to dad one(no sign on needed uses one_public as user). I must grant execute on the form procedures to one_public so I don't get security violation when a user tries to run it from website. Public can run forms they should without sign on. Signed on users can run their forms, but the contexts, which are activated in a logon trigger are not being enforced. I believe this is because to get to the webdb component(the form) the actual user signed on is one_public, not the end user who signed on. If I change the DAD for webdb to the webdb DAD, the public users are asked to sign on to see the forms they should see without needing a sign on. It wants them to sign on to the webdb relam. This is not the desired result. Is there any way to enforce the contexts in this scenario? Do IO need to create the forms in another relam? Am I total hosed? Is anyone still monitoring this forum seeing Webdb is old?? I hope some one can help me.....
Red Flag Submitted
Thank you for helping keep Tek-Tips Forums free from inappropriate posts. The Tek-Tips staff will check this out and take appropriate action.
Reply To This Thread
Posting in the Tek-Tips forums is a member-only feature.