APEX

Greetings. I'm working on a Custom Authentication (returning back from our Central Auth Server) and cannot get the startup of APEX to work. The app will run, but i always end up logged in as APEX_PUBLIC_USER instead of the "real" id.

-----"cut to the chase"

At this point, i am in a pl/sql proc (NOT inside Apex, but which can be executed by APEX_PUBLIC_USER) which knows fulll well what ID has been fully authenticated (succssfully), plus: server, DAD name, application number, page and all item set values to use to construct the apex url (even if deep into the app).

all I need to do is: establish the session with that userid and re-direct to it. (right?)



i've read all the ntlm white paper and searched and read numerous discussions about that on this forum. i think the steps i need are close to what is in the ntlp page sentry after the point:
-- application session cookie not valid --> define a new apex session.

i've tried modifying the remaining code with the main modifications being simply in how the URL is actually created because i know all the info (listed above).

I'm happy to post the code, but first am just wondering:

does this sound reasonable as a strategy, or am i "barking up the wrong tree"?
Is there any documentation (i've searched but come up empty) on wwv_flow_custom_auth_std.post_login?
If i have a deep link, and know the full URL query string, do I still need to set: wwv_flow_custom_auth.remember_deep_link (is there any doc on this?)

thanks for any help David S. - Tampa, FL