Typically, on the Autonomous Database when accessing the Internal/Administration Workspace, at some point you’ll need to create a new Workspace (and Schema).
As you see above, I supplied ADMIN as Workspace User. Doing so, only creates this as a Workspace User, not a Database user.
Following creation, you’ll find that you may be unable to login the workspace given the Workspace password that you just provided
This is because, the Manage Instance > Security > Security Settings > Current Workspace Authentication Scheme is set to Database Accounts on Autonomous Databases
Therefore I can only log in with a valid Database credentials. In my case the ADMIN user already exists on the Database (with a different password), so I could log in with that password (since the workspace setup just created an ADMIN user associated with this Workspace).
Alternatively, I could also create a new user:
and try to log in
However, I’m still unable to login until I create an APEX User and Associate it with the Workspace.
After creating the user… I can now log in with my Database Password
If I create an APEX application and want to Login with my new LUFC_USER (with APEX Authentication) then it would be the APEX Users’ password see picture below (i.e not the Database Password)
Contrary to other information, there is no requirement to match both the APEX Users Password and the DB Users password. The former is for Application Authentication, the latter for Workspace Authentication.
In Summary
If the Workspace Authentication is set to Database Accounts (ADB Default), then a Database Username and Password must be supplied. This will only allow Workspace login if there exists an APEX User, with the same name, associated with the Workspace you are signing in to.
The password associated with the APEX User is used for Sign-in to APEX Applications whose Authentication Scheme is set to Oracle APEX Accounts
Changing Builder Authentication
To view available Authentication Schemes click on Manage Instance > Security > Security Settings > Development Environment Authentication Schemes
When clicking on Oracle APEX accounts > Make Current Scheme, you can change your Workspace Authentication Scheme
Before you do this, check that the ADMIN > INTERNAL User.
Check the password is not Expired (see picture before)
Check you know the password (changing it if required).
After Applying the changes, please read the warning before proceeding. After proceeding do not log out of APEX.
Warning: Following the change… do not log out of the Internal Workspace. Use an incognito browser to ensure you can still log back in to the Internal Workspace. If you have any problems logging back in, change back to your original browser window and change it back to Database Accounts.
If you have accidentally logged out, you can set it back to DB accounts using PL/SQL.
BEGIN
apex_instance_admin.SET_PARAMETER('APEX_BUILDER_AUTHENTICATION','DB');
COMMIT;
END;
ENJOY
What’s the picture? An Aston Martin covered in snow in a wintry looking Harrogate