Context
Starting from server 5.7, manage roles and users will use
asadm. For reference, apply the following steps to dynamically enable security authentication in a rolling restart manner.
Method
- Quiesce the node.
- Stop the Aerospike server.
- Modify aerospike.conf file, the presence of a security stanza enables security and access control.
- Start the Aerospike Server.
- Using --single-node parameter to login with the default username admin and password admin.
- Create users and roles on the single node,
- Make sure security.smd file generated in /opt/aerospike/smd/security.smd
- Verify the created user is able to login
- Move to next node
Notes
security.smd will generate when uers/roles are created, however since the cluster is in a mix security mode. asadm is not able to create user/roles for all nodes, security.smd will need to be generated node by node.
Applies To Earliest Version
5.7
Applies To Latest Version
Current Version
