Re: [cx-oracle-users] Setting client_identifier upon connect()
Brought to you by:
atuining
From: Anthony T. <ant...@gm...> - 2012-08-24 16:20:49
|
On Fri, Aug 24, 2012 at 8:30 AM, Walter Dörwald <wa...@li...> wrote: > On 24.08.12 16:00, Anthony Tuininga wrote: > >> Hi, >> >> Yes, it actually is possible and was just implemented as requested by >> Rodney Barnett. 5.1.2 has this feature included. :-) > > > Not for client_identifier: You're right. I was thinking of clientinfo but that's different. Sorry about the confusion! I'll look into adding clientidentifier as well. Anthony > > $ python3.2 > Python 3.2.3 (default, Jul 20 2012, 17:32:16) > [GCC 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.1.00)] on > darwin > Type "help", "copyright", "credits" or "license" for more information. >>>> import cx_Oracle >>>> cx_Oracle > <module 'cx_Oracle' from > '/Users/walter/.local/lib/python3.2/site-packages/cx_Oracle-5.1.2-py3.2-macosx-10.6-x86_64.egg/cx_Oracle.so'> >>>> db = cx_Oracle.connect('u/p@db', client_identifier='foo') > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > TypeError: 'client_identifier' is an invalid keyword argument for this > function > > Servus, > Walter > > >> On Fri, Aug 24, 2012 at 6:57 AM, Dag Wieers <da...@wi...> wrote: >>> >>> Hi, >>> >>> I expect this to not be possible. I am in the situation where a tool >>> written in perl is allowed to access the database, but a tool using >>> python >>> is not (with the same credentials). When adding a symlink from ./perl to >>> /usr/bin/python and using that as the shebang does work. >>> >>> Given the fact that the client_identifier is so easily circumvented I was >>> wondering whether it would be possible to modify the client_identifier >>> used upon connect() rather than having to resort to such workarounds. >>> >>> (Yes, I know changing the ACL is probably the best way forward and is in >>> fact formally requested, but due to complex corporate processes this may >>> take weeks to get executed anyway...) >>> >>> I know it is possible to modify the client_identifier once connected, but >>> it seems useful to also be able to modify the client_identifier upon >>> connect, maybe as an argument to connect(). >>> >>> If it is not currently possible, could it be implemented in cx_Oracle ? >>> >>> Kind regards, >>> -- >>> -- dag wieers, da...@wi..., http://dag.wieers.com/ >>> -- dagit linux solutions, in...@da..., http://dagit.net/ >>> >>> [Any errors in spelling, tact or fact are transmission errors] >>> >>> >>> ------------------------------------------------------------------------------ >>> Live Security Virtual Conference >>> Exclusive live event will cover all the ways today's security and >>> threat landscape has changed and how IT managers can respond. Discussions >>> will include endpoint security, mobile security and the latest in malware >>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >>> _______________________________________________ >>> cx-oracle-users mailing list >>> cx-...@li... >>> https://lists.sourceforge.net/lists/listinfo/cx-oracle-users >> >> >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> cx-oracle-users mailing list >> cx-...@li... >> https://lists.sourceforge.net/lists/listinfo/cx-oracle-users >> > |