It is sufficient to remove the "-BUILTIN-" authentication function from your custom scheme and set that item to nullSorry, you lost me there. Would you mind making the changes you recommend to my application on apex.oracle.com so that the Invalid Login Credentials message is not generated on first page view?
The current 4.1 wwv_flow_custom_auth_std.post_login() does call the authentication function and in short behaves like login()Not sure I understand what means either. I must confess, I "stole" the page_sentry function from this forum a long time back, I don't really understand what it does, more than what the few comments explain. Could you please clarify the change in behaviour, if you don't mind?
We will provide a corrected version, maybe in 4.1.1, maybe in a one-off patchI am confused again. It appears that this is a (undocumented/inadvertent) change in authentication scheme behaviour introduced between 4.0.2 and 4.1 that breaks certain custom/page sentry-based authentication schemes like mine. But if there is a workaround, as you suggest above, what do you plan to fix in the "corrected version"? i.e. is this a defect in the product or just missing documentation?
[Hope you feel better]Thank you. Still working on that.
I logged in to your workspace and removed the value "-BUILTIN-" for the "Authentication Function Name"Since the ETA for 4.1.1 or a one-off patch to fix this is unknown, I don't want to hold up our upgrade to 4.1 just for this. But I am not looking forward to opening up all our apps to blank out that -BUILTIN- token. Is there a equivalent surgical SQL update you can recommend that our DBAs can do after the upgrade to 4.1? Thanks
Christian Neumueller wrote:Has this issue been assigned a bug number?
Since post_login() is a documented function, we will have to provide a version that is similar to the previous one, i.e. it should not call the pre authentication and authentication functions.
When I run the application (you can follow along at http://apex.oracle.com/pls/apex/f?p=24317:500 ), it throws an error
:G_APP_USER := :APP_USER;
Looks like another bug. This is getting to be annoying.
Error ERR-1002 Unable to find item ID for item "APP_USER" in application "24317". Unexpected error, unable to find item name at application or page level.