Licensing: only one API Token possible

Axon Server
1

Hello,

we downgraded from Axonserver EE to AxonIQ Professional Licensing model. Before we setup one API Token for each application (client) which connects to Axonserver.

Now we’re not able to add a API Token. It’s only allowed to configure one API Token.

In Axonserver Admin GUI the button is disabled:

Screenshot 2025-09-15 at 13.44.09
Screenshot 2025-09-15 at 13.44.092584×1650 240 KB

Using the api I got this error

Please note this token as this will only be provided once!
Error processing command 'register-application' on 'https://axonserver-01....:8024/v1/applications': HTTP/1.1 403  - {"message":"[AXONIQ-1700] Maximum number of applications reached","error":"LICENSE_ERROR","status":"AXONIQ-1700"}

But in AxonIQ console there is still 1 of 5 clients connected.

Should I use one single API Token for the clients?

2

Also I’m interested in the response to the above question.

3

Hi @MeikDev,

You are indeed correct that you should use the single API token generated for each of your applications.

Kind regards,

Silvano

4

I believe this does not answer the question. If I have a uService application where I want to restrict one of the services to only be able to use queries, I need for my application to use two tokens. The Original question was why this is restricted? The licence is connection based.

5

The subscription you have for AxonServer doesn’t support that usecase. If you require that level of permissions management, you need to switch to AxonServer Enterprise.

6

Ok, thanks. I needed to know if this was by design or if there was an issue in our installation. That clarifies it.

7

Hello Peter,

I’ve been reviewing this case in more detail. We have always intended for application tokens to be fully unlocked with the AxonIQ Professional subscription. However, due to a bug this was only granted for users in the license that is provided.

This bug has now been resolved. Your connected Axon Server is sent a new license file every 24 hours. This will happen for your prod environment in roughly 7 hours, and for your test environment in roughly 18 hours. These should include the permissions in your license file to create multiple access tokens for application.

Thank you for your patience, and for bringing this issue to our attention.

1 Like