This page describes an older version of the product. The latest stable version is 12.3.

Custom Security


Note

This section assumes that you are familiar with basic security concepts, and with XAP-specific security configurations. Before implementing custom security from scratch, consider the following alternatives:

GigaSpaces security was designed with customization in mind. There are numerous security standards and practices, so users can implement the built-in security features out of the box, or customize them to suit the needs of the industry and environment.

You can customize the security protocols for the following:

Packaging and Classpath

The most common scenario is for all services to share the same custom security. This is easily accomplished by placing the custom implementation classes in the lib/optional/security directory.

Note

You can use a different directory by configuring the com.gigaspaces.lib.opt.security system property.

<XAP root>/lib/optional/security/my-custom-security.jar

Processing Units can share a custom security implementation that may differ from that of the GSM and GSCs. In this case, the custom security JAR can be placed under pu-common.

<XAP root>/lib/optional/pu-common/my-pu-custom-security.jar

If each Processing Unit has its own custom security implementation, the custom security JAR can be part of the Processing Unit distribution.

<XAP root>/deploy/hello-processor/lib/my-processor-custom-security.jar
Note

We recommend that the custom security JAR contain only security-related classes.