| APEX_PUBLIC_USER authentication [message #690390] |
Thu, 14 August 2025 08:51 |
John Watson
Messages: 8988
Registered: January 2010
Location: Global Village
|
Senior Member |
|
|
I have a problem with one of our APEX environments: the APEX_PUBLIC_USER account keeps getting locked. It isn't a production system, it's used by any number of people for training, demos, stuff like that. I haven't worked out why it is getting locked. I have a solution that seems to work:
ALTER USER APEX_PUBLIC_USER NO AUTHENTICATION;
and now I can give it the wrong password any number of times and the account isn't locked. ORDS can still create its connection pool and APEX still works.
My question is, could this cause any problems? Particularly when using web services or the AI stuff? The installation doc for APEX 24.2 is clear, in section 6.3.4.3,
https://docs.oracle.com/en/database/oracle/apex/24.2/htmig/downloading-installing-apex.html#GUID-EE55AB65-51CC-450C-9675-C6010EE95630
it says
Quote:Run the following statement:
ALTER USER APEX_PUBLIC_USER IDENTIFIED BY new_password
Where new_password is the new password you are setting for APEX_PUBLIC_USER. You will use this password when creating the DAD in the sections that follow.
is that just out of date nonsense, or will my change to NO AUTHENTICATION actually break anything?
I have never really understood how ORDS sessions become APEX_PUBLIC_USER sessions, it certainly isn't the normal proxy authentication method, which is why I went for NO AUTHENTICATION rather than PROXY ONLY CONNECT.
Thank you for any insight.
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
