Community Tip - Learn all about PTC Community Badges. Engage with PTC and see how many you can earn! X
Hi,
is there a way to blacklist a remote device from connecting to the server using the remote thing name/identifier.
Currently we have some old remote devices out in the world using the same identifier to connect.
Unfortunately we aren't able to physically find these remote things to upgrade the edge servers (or disconnect them). Really just looking for a way to stop the Application log collecting these errors.
Thanks in advance
K
Solved! Go to Solution.
You can whitelist not blacklist unless that has been updated in recent versions.
I would say that ability to blacklist is a great suggestion though.
Too late to do unique appkeys?
appkeys do have white listing capability as well.
perhaps that can help at least to weed out the old devices.
Hi,
think this might have legs. Are you saying that you can blacklist certain appkeys?
K
You can whitelist not blacklist unless that has been updated in recent versions.
I would say that ability to blacklist is a great suggestion though.
Thanks for the replies. The remote devices of concern are all using the same particular appKey, which is different from all other devices.
Would you know, if I delete that appKey will that produce errors as well, or will it just refuse to connect?
It will just refuse connection if you delete the appkey
Hello @khayes1,
It should still produce an error, something along the lines of "Invalid AppKey", however you might be able to hide it by disabling this specific logger in $TWX_PLATFORM/logback.xml. I haven't tried it myself, but I don't see a reason why that wouldn't work.
Regards,
Constantine
Hi,
thanks, you were right about it still producing errors 'Missing AppKey'. Looked for the file 'logback.xml' that you referred to, but was unable to find it?
K
Hello @khayes1,
Try to create it with this content:
<configuration>
<logger name="com.thingworx.communications.platform.modules.DispatchingServerCommunicationModule" level="OFF"/>
</configuration>
This should switch off this logger, which means that you won't see pretty much any error messages related to invalid login, binding errors, etc. Even if it works, this is clearly a bad practice, so please use it carefully and only as a temporary solution.
If you really have to use it, then I would suggest that instead of turning the logger off, you can try using another appender for it, e.g. write those error messages to a separate log file. You can find more details by searching for "logback configuration", for example here: http://logback.qos.ch/manual/configuration.html
/ Constantine
Hi @khayes1.
If one of the previous responses answered your question, please mark the appropriate one as the Accepted Solution for the benefit of others on the community.
Regards.
--Sharon