Creation of profile using PASSWORD_VERIFY_FUNCTION ??? (Was "Security for a group of users ???")

From: <Wolfgang.Rothmayer_at_bmw.de>
Date: Fri, 31 Jul 1998 14:27:43 GMT
Message-ID: <35c1d09d.365672208_at_news.muc>



Hi there,

in my efforts to find a security mechanism a newsgroup member suggested to use the table PRODUCT_USER_PROFILE. The key point is, that up to now this seems only to work for ORACLE products (i.e. SQL*PLUS).
But we need some application level of security where some apps shall be granted to a user or a role but the most of other apps will be locked for all users.
This is especially needed for database access through ODBC connections (MS-ACCESS). I know that interessting data can be found in the table v$session in the fields OSUSER, TERMINAL, PROGRAM and MACHINE. With this fields an identification of an ODBC connection with MS-ACCESS can be done.

Another feature which can be used for security is the command CREATE PROFILE where a function (scripts) can be specified which is executed at logon of any user. This function can be specified with PASSWORD_VERIFY_FUNCTION. Now my questions:

Did anyone of you ever try this feature ?

Did you experience any problems with it ?

Could you kindly point me to samples where this feature is or has been used successfully ?

Did anyone of you use the table PRODUCT_USER_PROFILE for other than ORACLE applications ?
If so, are there any problems ?

What is the life cycle of the table v$session ?

Will I be able to use information of this table in a logon verifications scripts ?

Many, many thanks in advance for any input. Wolfgang. Received on Fri Jul 31 1998 - 16:27:43 CEST

Original text of this message