Skip to main content

Good morning,

our customers, for privacy reasons, do not want to give the account to access the database with sensitive information.

Our batch COBOL applications (no cics) are accessing the database with odbc using this statment like this:  

EXEC SQL

   CONNECT TO :WS-DB USER    :WS-USER USING    :WS-PASSWORD

END-EXEC.

The values of these variables are taken with the cobol command:

DISPLAY "HPASS" UPON ENVIRONMENT-NAME ACCEPT WS-PASSWORD FROM ENVIRONMENT-VALUE  

Our customers do not want to put in a ENVIRONMENT or into a script file.

there are alternatives?

thanks...


#ODBCESQL

Good morning,

our customers, for privacy reasons, do not want to give the account to access the database with sensitive information.

Our batch COBOL applications (no cics) are accessing the database with odbc using this statment like this:  

EXEC SQL

   CONNECT TO :WS-DB USER    :WS-USER USING    :WS-PASSWORD

END-EXEC.

The values of these variables are taken with the cobol command:

DISPLAY "HPASS" UPON ENVIRONMENT-NAME ACCEPT WS-PASSWORD FROM ENVIRONMENT-VALUE  

Our customers do not want to put in a ENVIRONMENT or into a script file.

there are alternatives?

thanks...


#ODBCESQL

Product, version, and platform, please.

There are always alternatives, but it's a little difficult to discuss them without basic information about the operating environment.

Good morning,

our customers, for privacy reasons, do not want to give the account to access the database with sensitive information.

Our batch COBOL applications (no cics) are accessing the database with odbc using this statment like this:  

EXEC SQL

   CONNECT TO :WS-DB USER    :WS-USER USING    :WS-PASSWORD

END-EXEC.

The values of these variables are taken with the cobol command:

DISPLAY "HPASS" UPON ENVIRONMENT-NAME ACCEPT WS-PASSWORD FROM ENVIRONMENT-VALUE  

Our customers do not want to put in a ENVIRONMENT or into a script file.

there are alternatives?

thanks...


#ODBCESQL

i'm using

SERVER FOR COBOL\\ SOA 5.1 on WINDOWS sytem and

SERVER EXPRESS 6.0 on  AIX system

i'm using ORACLE 11.2, Sql Server, Teradata, Udb db2 odbc driver's.

thanks

bye

Good morning,

our customers, for privacy reasons, do not want to give the account to access the database with sensitive information.

Our batch COBOL applications (no cics) are accessing the database with odbc using this statment like this:  

EXEC SQL

   CONNECT TO :WS-DB USER    :WS-USER USING    :WS-PASSWORD

END-EXEC.

The values of these variables are taken with the cobol command:

DISPLAY "HPASS" UPON ENVIRONMENT-NAME ACCEPT WS-PASSWORD FROM ENVIRONMENT-VALUE  

Our customers do not want to put in a ENVIRONMENT or into a script file.

there are alternatives?

thanks...


#ODBCESQL

In this case it is windows server 2008 r2 with Ms sqlserver 10

bye

Good morning,

our customers, for privacy reasons, do not want to give the account to access the database with sensitive information.

Our batch COBOL applications (no cics) are accessing the database with odbc using this statment like this:  

EXEC SQL

   CONNECT TO :WS-DB USER    :WS-USER USING    :WS-PASSWORD

END-EXEC.

The values of these variables are taken with the cobol command:

DISPLAY "HPASS" UPON ENVIRONMENT-NAME ACCEPT WS-PASSWORD FROM ENVIRONMENT-VALUE  

Our customers do not want to put in a ENVIRONMENT or into a script file.

there are alternatives?

thanks...


#ODBCESQL

For Windows, the simplest solution to improve the security of the database credentials in a case like this is to put them in a file, and set the ACL for the file so it's only readable by the account or accounts that the COBOL applications run under. Without knowing more about the architecture I can't suggest anything more specific, but that's certainly better than putting them in the environment, which has no security whatsoever.

Ultimately the COBOL applications that use ODBC need those credentials. All you can do is increase the work factor for an attacker trying to get them. Specific solutions depend on the customer's threat model, and what kinds of access users have to the system.

Good morning,

our customers, for privacy reasons, do not want to give the account to access the database with sensitive information.

Our batch COBOL applications (no cics) are accessing the database with odbc using this statment like this:  

EXEC SQL

   CONNECT TO :WS-DB USER    :WS-USER USING    :WS-PASSWORD

END-EXEC.

The values of these variables are taken with the cobol command:

DISPLAY "HPASS" UPON ENVIRONMENT-NAME ACCEPT WS-PASSWORD FROM ENVIRONMENT-VALUE  

Our customers do not want to put in a ENVIRONMENT or into a script file.

there are alternatives?

thanks...


#ODBCESQL

thanks, you've been very helpful

Terms & ConditionsAccessibility statement