You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Im not sure this is a bug I have logger install on two servers one for dev the other production. But for some reason I get different users names when logging. 1 always has the user a APEX_PUBLIC_USER as the user name (production 19.1) while dev server shows the user_name as the LDAP user who's logged into apex.
I just created a quick test and I called logger but got different user when the same use was logged into both.
Is this a bug Im not sure why they would be different the Oracle Apex workspace is the same on both hosts I copied from dev to production when we created the new workspace so they both have the same work_space_id and both have the same setting and apex version the only difference is that Oracle Database is 12.2c and the other 19.1c both are on apex 20.1
The text was updated successfully, but these errors were encountered:
As I said Im not sure if its me just making a mistake or a bug as I have the same settings on both hosts the only difference is the database version not Apex and all Logger version are the same
Hi Im not sure this is a bug I have logger install on two servers one for dev the other production. But for some reason I get different users names when logging. 1 always has the user a APEX_PUBLIC_USER as the user name (production 19.1) while dev server shows the user_name as the LDAP user who's logged into apex.
I just created a quick test and I called logger but got different user when the same use was logged into both.
Is this a bug Im not sure why they would be different the Oracle Apex workspace is the same on both hosts I copied from dev to production when we created the new workspace so they both have the same work_space_id and both have the same setting and apex version the only difference is that Oracle Database is 12.2c and the other 19.1c both are on apex 20.1
The text was updated successfully, but these errors were encountered: