Oracle APEX, a terrific low-code and rapid application development, ought to isolate developer credentials from application credentials. Running applications with developer-level credentials exposes low-code/no-code applications to risks. Please avoid these features. Read why now…
Oracle APEX includes user security features rooted firmly within Oracle. These features permit developers to list users, add users, assign user’s permissions/roles, and removing a user. When promoting a low-code and secure application, trusting then using Oracle’s security for user authentication and authorization will save time, effort, and costs. You gain the additional benefit of drawing on decades of Oracle’s experience in user security. I am presenting this article in two parts. Together, these articles examines the APEX_ACL and APEX_UTIL packages and several public views including APEX_APPL_ACL_USER, and APEX_WORKSPACE_USERS.
Storing large files in an Oracle database can be expensive and cumbersome. The expense comes from the size of the on-line disk storage and the efforts to run backups with archive logs. Oracle Cloud Infrastructure introduced a REST API for large object storage (multi-media files, etc.) This feature has been available with Amazon Web Services (AWS) for years. I wrote and published an API for AWS S3 storage using PL/SQL in 2016 and 2017. With AWS S3, a development team can reliably store binary large objects (BLOB / multimedia files) securely and cost effectively. In this article, I’ll explore the advantages and updates I have made to the AWS S3 package.
A key purpose of this blog entry is to communicate that we are publishing a template for PL/SQL-based API. It is located on my GITHub page (https://github.com/cmoore-sp/plsql-api.git) and communicates with a public website hosting public APIs.