I posted about my APEX upgrade to 19 yesterday, and someone was quick to point out to me that they believed I hadn’t covered all of the steps.
“What if your APEX instance needs to call web services?” they said. “You need to update your Access Control Lists.”
I hadn’t thought of that, so I logged onto one of my other APEX instances that was still at version 18, and checked the current ACLs
SYS> select acl,
2 principal,
3 privilege
4 from dba_network_acl_privileges
5 order by acl, principal, privilege;
ACL PRINCIPAL PRIVILEGE
-------------------------------------------------- -------------------- ----------
/sys/acls/oracle-sysman-ocm-Resolve-Access.xml ORACLE_OCM resolve
NETWORK_ACL_192DBA180AEB40AD98A73ACCD309FF8F APEX_180200 http
NETWORK_ACL_296C00CF7F2744BAB526D4C4E85FE189 GGSYS resolve
NETWORK_ACL_296C00CF7F2744BAB526D4C4E85FE189 GSMADMIN_INTERNAL resolve
4 rows selected.
I can see the potential issue here. On upgrade, I’ll have a new schema which would need the same ACLs granted as the existing APEX 18 schema. Then I went ahead and upgraded this instance to version 19, and lo and behold, check out this nice little touch in the upgrade.
SYS> select acl,
2 principal,
3 privilege
4 from dba_network_acl_privileges
5 order by acl, principal, privilege;
ACL PRINCIPAL PRIVILEGE
-------------------------------------------------- -------------------- ----------
/sys/acls/oracle-sysman-ocm-Resolve-Access.xml ORACLE_OCM resolve
NETWORK_ACL_0F93A8F653EC43DC9D90457B1151A330 APEX_190100 http
NETWORK_ACL_192DBA180AEB40AD98A73ACCD309FF8F APEX_180200 http
NETWORK_ACL_296C00CF7F2744BAB526D4C4E85FE189 GGSYS resolve
NETWORK_ACL_296C00CF7F2744BAB526D4C4E85FE189 GSMADMIN_INTERNAL resolve
5 rows selected.
The upgrade took care of the ACLs for me! That’s pretty cool.




Leave a reply to Connor McDonald Cancel reply