JR52986: DB2CONNECTOR SHOWS DECRYPTED USERNAME IN THE LOGS WHEN LOGIN FAILS WHILE PASSING AN ENCRYPTED USERNAME AS PARAMETER.

InfoSphere Information Server, Version 11.5 for Linux
InfoSphere Information Server, Version 11.5 for Windows
InfoSphere Information Server, Version 11.5.0.2 for Linux
InfoSphere Information Server, Version 11.5.0.2 for AIX
InfoSphere Information Server, Version 11.5.0.2 for Windows
InfoSphere Information Server, Version 11.5.0.1 for AIX

APAR status

• Closed as program error.

Error description

• When an encrypted username is passed as a parameter to Username
  property within DB2Connector, and the login fails, an error
  message as below is displayed:
  DB2_Connector_0: The connector could not establish a connection
  to DB2 database XMETA using user <decrypted username>.
  

Local fix

Problem summary

• DB2Connector shows decrypted username in the logs when login
  fails while passing an encrypted username as parameter.
  

Problem conclusion

• When an encrypted username is passed as a parameter to Username
  property within DB2Connector, and the login fails, an error
  message as below is displayed:
  DB2_Connector_0: The connector could not establish a connection
  to DB2 database XMETA using user <decrypted username>.
  
  This message has been corrected and will now not display
  encrypted username when login fails.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• R910 PSY

     UP

• R912 PSY

     UP