Greetings,
What is the use of the "Use OS Level Authentication" checkbox in the Oracle OCI PLug-ins. How does that work?. Kindly let me know your thoughts
Thanks & regards,
Badhri ...
Badhrinath Krishnamoorthy
www.cognizant.com
Use OS Level Authentication
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 3593
- Joined: Thu Jan 23, 2003 5:25 pm
- Location: Australia, Melbourne
- Contact:
Whenever I've seen that option in other products is means that the login to Oracle will use the network login that is running the process. This means you do not need to supply an Oracle login and password, it will attempt to use the network login and password, which is usually the user name you use to log into DataStage. I've found synchronised network and database logins to be a common practice with SQL Server implementations but not so common in Oracle.
Vincent McBurney
Data Integration Services
www.intramatix.com
Vincent McBurney
Data Integration Services
www.intramatix.com
We are using ORA OCI8 stage to connect to Oracle 817, DS5.1
We were actually looking in to going in for OS Authentication, to cover the audit points raised for password being shown in datastage logs and wrapper script logs.
During our try, we found that enabling the OS Authentication ( checking the box ), would require the Oracle init parameter REMOTE_OS_AUTHEN to be true. Support guys had confirmed that the parameter need to be TRUE for OS Authen to work.
Enabling REMOTE_OS_AUTHEN would open more security concerns, even oracle documentation cautions using these feature.
We were forced to drop the idea of going in for os authentication, and now are trying to make the password type as encrypted, so that ****** is displayed, and password read and decrypted inside the job itself in the job control.
Hope this info helps.
Karthi
We were actually looking in to going in for OS Authentication, to cover the audit points raised for password being shown in datastage logs and wrapper script logs.
During our try, we found that enabling the OS Authentication ( checking the box ), would require the Oracle init parameter REMOTE_OS_AUTHEN to be true. Support guys had confirmed that the parameter need to be TRUE for OS Authen to work.
Enabling REMOTE_OS_AUTHEN would open more security concerns, even oracle documentation cautions using these feature.
We were forced to drop the idea of going in for os authentication, and now are trying to make the password type as encrypted, so that ****** is displayed, and password read and decrypted inside the job itself in the job control.
Hope this info helps.
Karthi
Sorry for bringing the old topic up ..
I am wondering if there is anything else that we need to change on datastage side other than
a) Check OS level authentication box
b) Enter DB name, leave ID/pswd fields
c) get the DBAs to setup ops$userID on the unix server and REMOTE_OS_AUTHEN = true
thanks in advance.
I am wondering if there is anything else that we need to change on datastage side other than
a) Check OS level authentication box
b) Enter DB name, leave ID/pswd fields
c) get the DBAs to setup ops$userID on the unix server and REMOTE_OS_AUTHEN = true
thanks in advance.
thank you
- prasad
- prasad