[
https://issues.jboss.org/browse/TEIID-2856?page=com.atlassian.jira.plugin...
]
Marco Grigull commented on TEIID-2856:
--------------------------------------
JDBC
2014-02-19 15:03:29,844 DEBUG [org.teiid.SECURITY] (New I/O worker #2:) Logon successful,
created session: sessionid=xDc8ma7VHRAG; userName=protected_user@teiid-security;
vdbName=raw; vdbVersion=1; createdTime=Wed Feb 19 15:03:29 EST 2014; applicationName=JDBC;
clientHostName=<user_reported_hostname>; clientHardwareAddress=null;
IPAddress=10.x.x.x; securityDomain=teiid-security; lastPingTime=Wed Feb 19 15:03:29 EST
2014
The IPAddress was incorrect, it was not related to the client or the server in any way.
The clientHostName reported did not have a reverse entry and reported a forward only
hostname
ODBC/psql client:
2014-02-19 14:50:46,606 DEBUG [org.teiid.SECURITY] (New I/O worker #3:) Logon successful,
created session: sessionid=IRhteOhG5nj1; userName=another_user@teiid-security;
vdbName=public; vdbVersion=1; createdTime=Wed Feb 19 14:50:46 EST 2014;
applicationName=ODBC; clientHostName=null; clientHardwareAddress=null; IPAddress=null;
securityDomain=teiid-security; lastPingTime=Wed Feb 19 14:50:46 EST 2014
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
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