Pau Lo
asked on
dba_users entry for application accounts
If you have an oracle 10g database, residing behind a business application (i.e. for arguments sake let’s say your corporate finance system), is it common for the dba_users to be populated with an account per application user? I thought it would be common for the accounts in dba_users to only be those used for database administration, and perhaps some data analysts, so I was a bit shocked when I noticed anyone who has a login account for the application front end to have an entry in dba_users. Is this kind of authentication common? Does it have a specific name? I assume this is down to how the applicaiton was programmed, as for other apps that have a backend oracle database, there definately isnt an entry is dba_users per application (front end) accounts.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
>> then neither will the account that they use to login to the application
Good bet.
>>however the application is still programmed in such a way
It's code... You "can" do whatever you want.
Just not sure why you would want to write code to handle something Oracle handles for free?
You can set up PROFILE's to control all of this. Then the app just needs to account for the error messages it receives form the database.
Good bet.
>>however the application is still programmed in such a way
It's code... You "can" do whatever you want.
Just not sure why you would want to write code to handle something Oracle handles for free?
You can set up PROFILE's to control all of this. Then the app just needs to account for the error messages it receives form the database.
ASKER
I assume thats those that are stored within the file dba_users:profile , and then marry those up to the values held in dba_profiles. if say for example password verify function says "default", what exactly does that mean. If it says something else, where can you actually see the password verify function to see what its enforcing.
>>I assume thats those that are stored within the file dba_users:profile , and then marry those up to the values held in dba_profiles.
Correct.
>>if say for example password verify function says "default", what exactly does that mean.
Check out: Oracle Password Management Policy [ID 114930.1]
>>If it says something else, where can you actually see the password verify function to see what its enforcing.
It's a stored function. If it is set, you can view the source just like any other function.
It could possibly be WRAPped (never tried this with a password function). If so, it's encrypted. There are claims that WRAPped code can be decrypted but I've never tried.
Correct.
>>if say for example password verify function says "default", what exactly does that mean.
Check out: Oracle Password Management Policy [ID 114930.1]
>>If it says something else, where can you actually see the password verify function to see what its enforcing.
It's a stored function. If it is set, you can view the source just like any other function.
It could possibly be WRAPped (never tried this with a password function). If so, it's encrypted. There are claims that WRAPped code can be decrypted but I've never tried.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER