Description
I've found we have a enum GridRestCommand.CLUSTER_ACTIVE,
but looks like it is not supported by GridRestProcessor and
enum SecurityPermission doesn't support any permission for cluster activation.
Also CLUSTER_INACTIVE has same issues.
So, cluster can't be activated with security plugin due to ERROR.
See userlist thread for details [1]
id=d2e2b816-61e3-47ff-9d88-ae4c8b3eb2ae, login=null 10-23 20:48:30.051 [rest-#47%cdev_cluster%] ERROR internal.processors.rest.GridRestProcessor - Client request execution failed with error. java.lang.AssertionError: Unexpected command: CLUSTER_ACTIVE at org.apache.ignite.internal.processors.rest.GridRestProcessor.authorize(GridRestProcessor.java:817) at org.apache.ignite.internal.processors.rest.GridRestProcessor.handleRequest(GridRestProcessor.java:250) at org.apache.ignite.internal.processors.rest.GridRestProcessor.access$100(GridRestProcessor.java:91) at org.apache.ignite.internal.processors.rest.GridRestProcessor$2.body(GridRestProcessor.java:157) at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at
[^http://apache-ignite-users.70518.x6.nabble.com/Cannot-activate-Ignite-with-custom-security-plugin-tt17687.html]