Hi Dojo,
When I look at all the open connections via the SLNet Client Test tool, I noticed that there is a connection with the name 'HTML5 App (Administrator...' which I would not expect. If I recall correctly, this naming of a connection implies that a user is connected using one of the web apps (e.g. dashboards). At the moment, there is no one connected. I also wouldn't expect to see 'Administrator' here. Is this some kind of core connection? I notice that it is constantly polling the DMA status. (which causes my SLNet log to be spammed a bit)
The web APIs have indeed one persistent admin connection to check certain info (eg cloud connectivity status) and build up some globally available cache. This connection is created during initialization of the web APIs and will try to reconnect automatically if its connection would be closed for whatever reason.
It has been there for years
Must have missed it for all this time…
Would it be possible to override either the ClientDisplayName or ClientApplicationName of that connection, to make it more clear that it is a persistent connection that is controlled from the software and that’s not an admin connection from a user (like it looks now)? Thanks in advance
It is fairly new (10.3.6/10.3.0[CU4]) that SLNet will now regularly do a request on the WebAPIs to make sure that it is running, to speed up the first page load when a user opens one of the web apps. Before this, the WebAPIs didn’t start up and you didn’t have this persistent administrator connection until you opened one of the web apps or until another app did a request on the WebAPI.
The DMA status polling is not done directly by the WebAPI, it is CloudGateway who is polling the WebAPI which forwards it to SLNet. Maybe we can apply some subscription+caching in the WebAPI to improve this.
Not sure but maybe it's a scheduled BPA test? I saw BPAs making connections as 'administrator', and those can be scheduled. Just a guess...
Ok, thanks! I assume this is something fairly recent? Never noticed this in the past.