<![CDATA[Web API Authentication Question: Bearer Token vs. Session-Id]]>I'm facing an issue with the Web API authentication on my setup (Ubuntu server with Tomcat 9).
I can authenticate and make API calls successfully when using a temporary session-id
obtained via the login endpoint. However, when I try to use a permanent API token (generated in the Management Console), I consistently get I consistently get error: 46 (NXSL_CLASS_NOT_FOUND)
My main question is: should authentication with permanent API tokens (Bearer Tokens) work as expected? Or for automation scripts, is the correct approach to always fetch a temporary Session-Id first?

Selected June 17 2025 12:51:50.png

Selected June 17 2025 12:52:06.png

]]>https://forum.netxms.org/topic/8196/web-api-authentication-question-bearer-token-vs.-session-idRSS for NodeFri, 13 Nov 2026 08:37:09 GMTTue, 17 Jun 2025 15:53:07 GMT60<![CDATA[Reply to Web API Authentication Question: Bearer Token vs. Session-Id on Wed, 25 Jun 2025 13:49:27 GMT]]>Tokens generated from Management Console are intended for different things - currently I think only for publishing network maps.
So yes, current way it to get temporarily session id.

UPD: actually permanent tokens are supported in the new API - the one that is server module and is currently under development. But not in the old one.

]]>https://forum.netxms.org/post/34555https://forum.netxms.org/post/34555Wed, 25 Jun 2025 13:49:27 GMT