I've just noticed that about a quarter of the records in T_WEB_SESSION_SESSION have the IP address of 10.10.6.9 with the earliest instance being the day we switched over to TNEW last year. Does anyone know why this IP is showing up and not the user's real IP like all the other records?
I am not a engineer, but I know enough to get into trouble. I noticed this with tablets and phones, specifically apple on our wifi. I know there is a command to show users dchp ip rather than the 10.×.×.×. I would assume the same would apply to the web server and your network setup. But, either way its fine.
dup
The user accessing your website shouldn't connect directly to the API. If you are using TNEW, the user requests a page from TNEW, and TNEW makes all of the calls to the API, managing each of those users' API sessions. But for every session, it's still TNEW making the call to the API and getting assigned the session key.
I would expect that if you identified what 10.10.6.9 was on your network, you would find it to be some networking infrastructure sitting between your API server and your internet connection. But on the other hand, this table isn't really documented anywhere so who knows what they're doing with it. I just ran SELECT DISTINCT IP FROM t_web_session_Session on my DB and got only 15 unique results, half of which aren't IP addresses at all. But I do see the same thing where one particular LAN IP is responsible for all of the TNEW calls.
Thanks, Gents. We do some sessions work on our site outside of TNEW so I'm sure that is involved here too. The weird thing is we don't use the 10.x.x.x range at all internally which is why I'm thinking TNEW. Maybe I'll open a ticket.
It's most likely the one of the internal TNEW addresses. This has been a pet peeve of mine for ages; TNEW fills in their own IP instead of the remote address of the user creating the SessionKey
Hmm. Is this happening to ALL your records in that table, Chris?
No it's not all of the addresses; we have quite a few non-TNEW uses of Tessitura so I'm not sure but I distinctly remember 0.0.0.0 and blank entries as well as 10.X.X.X-TNEW entries from the past.
I am also seeing "TNEW-Diagnostics" listed as an IP now.
Previously I was able to navigate to the listed IP(s) using my RAMP desktop but since our recent upgrade I am no longer able to do this. The 10.X.X.X IP was just the internal-facing IP of our TNEW site.
Just an update: This issue was fixed in the 6.3.0 release of TNEW. Issue #TNEXWEB-11499. I find it very handy to bookmark the release notes page.