Axon Reference Guide
AxonIQDownload Axon
Search…
4.5
Introduction
Architecture Overview
Axon Server
Release Notes
Getting Started
Quick Start
Axon Framework
Introduction
Messaging Concepts
Commands
Events
Queries
Sagas
Deadlines
Testing
Serialization
Tuning
Monitoring and Metrics
Spring Boot Integration
Modules
Axon Server
Introduction
Installation
Administration
Security
SSL
Access Control
Access Control - Standard Edition
Access Control - Enterprise Edition
Access Control - Client Applications
Access Control - CLI
Access Control - API
Access Control - LDAP
Access Control - OAuth 2.0
Performance
Migration
Extensions
Spring AMQP
JGroups
Kafka
Kotlin
Mongo
Reactor
Spring Cloud
Tracing
Appendices
A. RDBMS Tuning
B. Message Handler Tuning
C. Meta Annotations
D. Identifier Generation
E. Axon Server Query Language
Powered By GitBook
Access Control - CLI
When access control has been enabled, you may initially find yourself without a user account for the UI. Cluster templates can be used to combine the initial configuration of your replication groups, registrations of client application, and a core set of user accounts, but you can also use the CLI to do this. For this you still need an admin-level token, which for Axon Server SE can be configured in the properties. For Axon Server EE such a token is by default generated by Axon Server itself, and stored in a file named "./security/.token". This default location is known by the CLI, so if you run in in the working directory of Axon Server, it will check for that file and automatically use the token. If you have overridden the location or provided your own file with a token, for example to ensure that all nodes use the same token, then you must use the "-t <token>" option to provide it to the CLI.
Previous
Access Control - Client Applications
Next
Access Control - API
Last modified 4mo ago
Copy link