[
https://issues.jboss.org/browse/TEIID-2856?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-2856.
-----------------------------------
Fix Version/s: 8.7
Resolution: Done
Added the client ip as known to the server for ODBC.
Updated the JDBC client side logic to use the actual connection to determine the local
address, rather than just getLocalHost.
IP address incorrectly exposed via SECURITY logger
--------------------------------------------------
Key: TEIID-2856
URL:
https://issues.jboss.org/browse/TEIID-2856
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 8.5
Environment: RHEL6 linux 2.6.32-431.1.2.el6.x86_64 #1 SMP Sun Nov 24 09:37:37 EST
2013 x86_64 x86_64 x86_64 GNU/Linux
jbossas-standalone 7.2.1 6.Final_redhat_10.1.ep6.el6
Reporter: Marco Grigull
Assignee: Steven Hawkins
Fix For: 8.7
After configuring a logger for org.teiid.SECURITY debug level, fields for IP address
information appears to be supplied by the client and not observed from the connection
itself (odbc connections). It is reported as null for psql based connections.
This had previously been reported as TEIID-1586 and TEIID-1672 . IT still presents an
issue where audit trail is required.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira