e:\ords\ords-23.3.0.289.1830\bin\database\default\pool.xml
e:\ords\ords-23.3.0.289.1830\bin\database\myusername\pool.xml
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd">
<properties>
<entry key="db.username">myusername</entry>
<entry key="db.password">mypassword</entry>
<entry key="db.connectionType">basic</entry>
<entry key="db.hostname">myservername</entry>
<entry key="db.port">myport</entry>
<entry key="db.servicename">myservicename</entry>
<entry key="security.requestAuthenticationFunction">myusername.owa_custom.authorize</entry>
<entry key="jdbc.InitialLimit">10</entry>
<entry key="jdbc.MinLimit">10</entry>
<entry key="jdbc.MaxLimit">50</entry>
</properties>
Seeing the following in the catalina.log:
Mapped local pools from E:\ORDS\ords-23.3.0.289.1830\bin\databases:
/pls/apex/ => default => VALID
/pls/apex/myusername/ => myusername => VALID
All the searches are leaving me perplexed. I'm not sure how I can get the owa_custom.authorize function to be called like it once was with OHS and mod_plsql in the dads.conf:
PlsqlAuthenticationMode CustomOWA