This content has been marked as final. Show 2 replies
according to the recently published Oracle Whitepaper [url http://www.oracle.com/technetwork/developer-tools/apex/learnmore/apex-oam-integration-1375333.pdf]Integrating Oracle Application Express with Oracle Access Manager you need the OHS in front of the APEX Listener to support that scenario.
The APEX Listener doesn't support that kind of CGIEnvironment variables. There have been a few posts about people who patched the APEX Listener to extend it with own filters to support additional headers/functionality, but that's not officially supported.
If OHS is required to solve this problem (e.g. equivalent functionality to the PlsqlCGIEnvironmentList parameter from the dads.conf), then we are potentially making our configuration more complex by adding the APEX Listener to our existing OHS + mod_plsql. The whole idea of moving to the APEX Listener (aside from support for RESTful web services and other enhancements) was to simplify the configuration and run away from OHS (and all of its version control issues) + mod_plsql.
Is there a plan to enhance the APEX Listener in a future release to allow equivalent functionality to the PlsqlCGIEnvironmentList parameter? If so, we could remove the dependency on OHS and mod_plsql. That would be greatly appreciated!