axon.axonserver.token=<token>. The Axon Server connector will use this to authenticate the client to the server.
axonserver.properties, you must register applications with specific roles. Please do note that you'll need either a user with
ADMINlevel access to do this in the UI, or access to the system token for use with the CLI.
register-application" command. This command will return the token to use, which can be specified on the commandline, or generated by Axon Server. Note that this token is only generated once; if you lose it you must delete the application and register it again to get a new token. The command
register-applicationhas several options:
--applicationspecifies the name of the application.
--rolesspecifies the roles of the application. Specify multiple roles by giving a comma separated list, e.g. "
--descriptionspecifies a description of the application, which will be shown in overviews.
--tokencan be used to specify the token you want to use for a newly registered application.
--propertyadds an application specific property. These properties will be provided to any plugin processing messages from/for that application.
--access-tokenspecifies the access token to authenticate at the server to which the command is sent to. For SE this should be the same as the (admin) token set in the properties. For EE this should be the security token discussed above.
--servercan be used to specify the URL to the server that the command needs to be sent to. If this is not supplied it connects to "
http://localhost:8024" by default.
--httpswill cause the CLI to use TLS, in effect changing the URL to "
https://localhost:8024". Note that if you also want to change the port, you'll have to use "
-S", in which case you can leave out "
--insecure-sslwill tell the CLI that Axon Server is using a certificate which is not signed by a known CA, for example when using self-signed certificates.