Social Sign-in Provider will not work if Apex workspace name is the same with Ords pool name
(Doc ID 3006116.1)
Last updated on APRIL 09, 2024
Applies to:
Oracle REST Data Services - Version 23.4 and laterInformation in this document applies to any platform.
If have a workspace named for example "service 1" and then make an ORDS pool named ""service1", the url for the pool service1 will look like this : host:port/ords/service1 and if access the workspace service1, the url will result in :host:port/ords/services1/r/service1.
This creates ambiguity and the social sign in will not work every time. There are already two bugs to fix this but the workaround for the moment is to use different names for workspace in apex and pool in ords
Goal
CAUSE
------------
The workspace name is the same with the ORDS pool name
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Goal |
| Solution |
| References |