Versions Compared

Old Version 21

changes.mady.by.user Grace Meilen

Saved on

compared with

New Version 22

changes.mady.by.user Swapnil Bawaskar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: adding security-manager to server

...

  1. Copy the above "security.json" file into locator's directory (locator1 in the example below) or make it available on the classpath using the --classpath option while starting the locator.

  2. Using gfsh, start a locator with security activated.

    Code Block
    languagebash
    gfsh> start locator --name=locator1 \
    --J=-Dgemfire.security-manager=org.apache.geode.security.templates.SampleSecurityManager

  3. Similarly, start a server

    Code Block
    gfsh> start server --name=server1 --locators=localhost[10334] --J=-Dgemfire.security-manager=org.apache.geode.security.templates.SampleSecurityManager

  4. Start a new instance of gfsh and connect with one of the users defined in your JSON file. The super-user should be allowed to do everything in gfsh.

    Code Block
    gfsh> connect --locators=localhost[10334] --user=super-user --password=1234567

  5. Disconnect and reconnect with a user with lesser privileges:

    Code Block
    gfsh> disconnect
gfsh> connect --locators=localhost[10334] --user=joebloggs --password=1234567
gfsh> stop server --name=server1
An error occurred while attempting to stop a Cache Server: Subject does not have permission [CLUSTER:READ]
 
  6. Currently, changes to the security.json file require the locator to be restarted.

...