Stef Mientki wrote:
<cut explanation>
What you want is pretty hard as long as the data source is not centrally
protected with a password. That is you have a database on a server you
only access, there is a central db but access to it is restricted to the
admin, everybody else has a unique login name and a 'personal' database
which is a view on the central database.
Authentication must be done with any of the single sign on solutions
available, probably the most likely one is Microsoft's kerberos
implementation.
However it might be good enough to fetch the username from the
environment variables and use that to build custom queries inside your
application to get the data from the central resource.
As long as somebody is not using your standard database credentials to
directly go to the data or fiddles with your program and changes the
part where it fetches the username from the environment, you should have
hidden the security flaw sufficiently to appear to be protected.
--
MPH
http://blog.dcuktec.com
'If consumed, best digested with added seasoning to own preference.'
--
http://mail.python.org/mailman/listinfo/python-list
