by Allistar Melville >> Fri, 21 Nov 2003 1:19:28 GMT
Hi there,
We provide a relational view for our schema which exposes the majority of the database to ODBC compliant applications. We wish to provide proper security so that the username and password passed in is validated and that this user is allowed to access ODBC.
The Global::isUserValid method seems to be the most appropriate way of achieving this. This problem is that this method is called for all database connections, not just ones from the ODBC driver.
The question is this:
How, in the Global::isUserValid method can I determine that the current node/process is from the ODBC driver and not from a standard JADE client connection?
A method on the node or process call like "isFromODBC" would be great, but alas no such method exists. I will try and see if I can get this information from Windows, possibly by seeing if jadodbc.dll is an open module in this processes list of modules.
Has anyone implemented security for ODBC connections that is not also applied for other types of connection?
Thanks,
Allistar.
--
------------------------------------------------------------------
Allistar Melville
Software Developer, Analyst allistar@silvermoon.co.nz
Auckland, NEW ZEALAND
Silvermoon Software
Specialising in JADE development and consulting
Visit us at: http://www.silvermoon.co.nz
*NEW* Simple web access to Jade at: www.silvermoon.co.nz/jhp.html ------------------------------------------------------------------