I'm not familiar with DBAACCOUNT authentication. What I can say is that APEX does not support OID authentication for logins into the APEX application development environment. However, it does support OID logins for end-user access. I've been told that providing OID logins to the development environment is something that is planned for a future release. On Wed, Jun 24, 2009 at 5:27 AM, Johnson, George <George.Johnson@xxxxxxx>wrote: > Good day all, I was wondering if I could bother the APEX > developers/admins on the list. > > I have been asked to release an application to our new UAT APEX kit > and we would like to enable DBACCOUNT authentication. All our DB users are > authenticated via OID. When I attempt to login into any APEX application > with DBACCOUNT authentication enabled, it refuses to let the user in if the > user is OID authenticated. If I then change the DB account to have a local > DB password, not OID GLOBAL, then APEX authenticates fine. > > Has anyone run into this situation, if so would you be willing to > share any pointers or workarounds? > > RDBMS: 10.2.0.3 > Separate OHS home for the Apache > APEX v3.2 > All on the same Sun Solaris 10 SPARC server. > > Kind regards > > * * > > Please consider the environment before printing > > * > ******************************************************************************************** > * > > This message contains confidential information and is intended only for the > individual or entity named. If you are not the named addressee you should > not disseminate, distribute or copy this email. > > Please notify the sender immediately by e-mail if you have received this > e-mail by mistake and delete this e-mail from your system. E-mail > transmission cannot be guaranteed to be secure or error-free as information > could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, > or contain viruses. The sender therefore does not accept liability for any > errors or omissions in the contents of this message which arise as a result > of e-mail transmission. If verification is required please request a > hard-copy version. This message is provided for informational purposes and > should not be construed as an invitation or offer to buy or sell any > securities or related financial instruments. GAM operates in many > jurisdictions and is regulated or licensed in those jurisdictions as > required. > > To the extent this email has been sent to you by any GAM company domiciled > in the EU, being GAM (U.K.) Limited, GAM Sterling Management Limited, GAM > International Management Limited, GAM London Limited, GAM Fund Management > Limited, or GAM Fonds Marketing GmbH i.L., please note the following details > in respect of each such company: - GAM (U.K.) Limited (a company limited by > shares and registered in England and Wales with company number 01664573); - > GAM Sterling Management Limited (a company limited by shares and registered > in England and Wales with company number 01750352); - GAM International > Management Limited (a company limited by shares and registered in England > and Wales with company number 01802911); - GAM London Limited (a company > limited by shares and registered in England and Wales with company number > with Company Number 00874802) Each of Registered Office: 12 St. James's > Place, London, SW1A 1NX > > GAM Sterling Management Limited, GAM International Management Limited and > GAM London Limited are each authorised and regulated by the Financial > Services Authority. GAM Fund Management Limited (a company limited by shares > and registered in Ireland with no. 156828) of Registered Office: George's > Court 54-62 Townsend Street Dublin 2, Ireland > > GAM Fonds Marketing GmbH, i.L. (a company limited by shares and registered > in Germany under No. HRB 66857) of Friedrichstrasse 154, D-10117 Berlin, > Germany. The competent Commercial Register is “Amtsgericht Charlottenburg“ > in Berlin. Liquidator: Daniel Durrer. > -- Rumpi Gravenstein