Documentation Inaccuracy: Access Control in Axon Server SE
zambrovski opened this issue · 0 comments
zambrovski commented
Axon Server documentation promotes usage of the access token and access admin token for administration if the access control is activates. In addition, the description of AxonServer CLI states that the management of the applications is an enterprise-only feature.
See:
- https://docs.axoniq.io/reference-guide/axon-server/administration/admin-configuration/command-line-interface#application
- https://docs.axoniq.io/reference-guide/axon-server/administration/admin-configuration/configuration#configuration-properties
I ran into a bug upgrading from 4.6.11 to latest 2023.2.2 SE and asked @MGathier for help. As he explains in this post: https://discuss.axoniq.io/t/unable-to-connect-after-upgrade-from-4-6-11-to-axonserver-2023-2-x/5292/6 some things have changed in Axon Server SE:
- Axon Server doesn't honor the
accesscontrol.tokenfrom the config file / env variable - Axon Server doesn't honor the
accesscontrol.admin-tokenfrom the config file / env variable - The application MUST be created in order to connect using access control, and the creation works indeed with Axon Server SE (proved, works fine)
I believe this behavior is just fine, but the docs needs to be updated reflecting the change in the Axon Server SE.