Discussions
Categories
- 381.9K All Categories
- 2.1K Data
- 207 Big Data Appliance
- 1.9K Data Science
- 447.4K Databases
- 220.8K General Database Discussions
- 3.7K Java and JavaScript in the Database
- 23 Multilingual Engine
- 516 MySQL Community Space
- 464 NoSQL Database
- 7.8K Oracle Database Express Edition (XE)
- 2.9K ORDS, SODA & JSON in the Database
- 471 SQLcl
- 3.9K SQL Developer Data Modeler
- 185.9K SQL & PL/SQL
- 20.9K SQL Developer
- 292.7K Development
- 7 Developer Projects
- 124 Programming Languages
- 289.4K Development Tools
- 95 DevOps
- 3K QA/Testing
- 645.5K Java
- 23 Java Learning Subscription
- 36.9K Database Connectivity
- 150 Java Community Process
- 104 Java 25
- 22.1K Java APIs
- 137.8K Java Development Tools
- 165.3K Java EE (Java Enterprise Edition)
- 16 Java Essentials
- 143 Java 8 Questions
- 85.9K Java Programming
- 79 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.2K Java SE
- 13.8K Java Security
- 197 Java User Groups
- 24 JavaScript - Nashorn
- Programs
- 243 LiveLabs
- 35 Workshops
- 10.2K Software
- 6.7K Berkeley DB Family
- 3.5K JHeadstart
- 5.8K Other Languages
- 2.3K Chinese
- 166 Deutsche Oracle Community
- 1.2K Español
- 1.9K Japanese
- 225 Portuguese
Unable to setup BasicAuth in ORDS
Hi, I am trying to secure a web service using BasicAuth in ORDS via APEX. But it gives me error 401 Unauthorised. I have tried setting up privileges and roles. While setting up Privilege and pattern, I got this error. As per doc below, it should work but I am unable to understand why pattern doesn't.
https://blogs.oracle.com/cloud-infrastructure/post/ords-basic-authentication-with-oracle-apex
Answers
-
i can't tell by your screenshot what pattern you're trying to input
-
It is /DIST-INV/*
-
that should work, if you make the pl/sql api call manually or if you use database actions to create/edit the ORDS Priv, does it work?
-
Manual PLSQL execution works fine. See screenshot below.
Without Basic Auth the API call also works fine, when I choose Inherit auth from Parent and didnt make any auth related changes to ORDS.
-
sounds like an APEX bug to me then...
