it's filed as an enhancement request and not as a code bug. I don't know when this will be implemented, as #5278049 is assigned to the PL/SQL team and not to the APEX team. APEX does support several built-in authentications and you can also build your own custom schemes. If your question was APEX releated, please tell us your requirements, so we might help.
Thanks for explanation.
My task is migrate many web applications writen with modplsql to use embedded PL/SQL gateway (EPG).
Problem in custom athentication. Our applications use PerPackage custom authentication metod, which not implemented in EPG. How can i workaround that with minimum modifications in application source?
EPG certainly can be used in some scenarios, but I'm still wondering why you want to switch from OHS. Apparently, the existing setup already works for you. It's bound to be faster than EPG and OHS has a lot more configuration options, e.g. for performance and security.
If CustomOWA is not supported in EPG, you might be able to create a workaround by using other hooks that EPG provides, e.g. request-validation-function and some dynamic PL/SQL, based on HTTP headers. However, this is all unrelated to APEX, which this forum is all about. If other posters can not provide help, maybe you should ask in the PL/SQL forum.